CVE-2026-68147fscrypt: Avoid dynamic allocation in fscrypt_get_devices()
- 7.8HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 97% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: fscrypt: Avoid dynamic allocation in fscrypt_get_devices() When a blk_crypto_key starts being used or is evicted, fs/crypto/ calls fscrypt_get_devices() to get the filesystem's list of block devices, then iterates over them and calls blk_crypto_config_supported(), blk_crypto_start_using_key(), or blk_crypto_evict_key() on each one. Currently, the block device pointers are placed in a dynamically allocated array. This dynamic allocation is problematic because: - It can fail, especially at the fscrypt_destroy_inline_crypt_key() call site when it's invoked for inode eviction under direct reclaim. - fscrypt_destroy_inline_crypt_key() doesn't handle the failure. It just zeroizes and frees the blk_crypto_key without calling blk_crypto_evict_key(). That causes a use-after-free. For now, let's fix this in the straightforward and easily-backportable way by switching to an on-stack array. Currently the fscrypt multi-device functionality is used only by f2fs, which has a hardcoded limit of 8 block devices. An on-stack array works fine for that. (Of course, this solution won't scale up to large number of block devices. For that we'd need a different solution, like moving the block device iteration into the filesystem. Or in the case of btrfs, which will only support blk-crypto-fallback, we should make it just call blk-crypto-fallback directly, so the block devices won't be needed.)
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 9 days later
· 9 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 97% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < bab016bb80d74a9d1f7d4121a7fc1cb529b470e0
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < 4462ac3d90e897dda52ce4b6af2d526ddae835a8
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < 97a688563be71ec6fefc071aff69a66c69dbe244
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < 81ea8e8221853950c47dac7164f27c63a96f8f86
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < bc2d630296e0e049210ec05ff08459a6893ae749
- affected 22e9947a4b2ba255888541bd0111cf00b9b16586 – < 6fe4e4b8259e1330945b5f3c9476e08473b8e0e8
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/bab016bb80d74a9d1f7d4121a7fc1cb529b470e0 (opens in a new tab)
- https://git.kernel.org/stable/c/4462ac3d90e897dda52ce4b6af2d526ddae835a8 (opens in a new tab)
- https://git.kernel.org/stable/c/97a688563be71ec6fefc071aff69a66c69dbe244 (opens in a new tab)
- https://git.kernel.org/stable/c/81ea8e8221853950c47dac7164f27c63a96f8f86 (opens in a new tab)
- https://git.kernel.org/stable/c/bc2d630296e0e049210ec05ff08459a6893ae749 (opens in a new tab)
- https://git.kernel.org/stable/c/6fe4e4b8259e1330945b5f3c9476e08473b8e0e8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55532 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68147)Record last updated .