VDB

CVE-2026-68147

CVE-2026-68147 PUBLISHED CVSS 7.8 HIGH

fscrypt: Avoid dynamic allocation in fscrypt_get_devices()

Reported by linux · Published August 10, 2026

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.)

EPSS 0.14% · 3.0th percentile

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score
0.14%
3.0th percentile

Affected products

VendorProductVersions
LinuxLinux22e9947a4b2ba255888541bd0111cf00b9b16586, 22e9947a4b2ba255888541bd0111cf00b9b16586, 22e9947a4b2ba255888541bd0111cf00b9b16586
LinuxLinux6.1, 0, 6.1.183
linuxlinux_kernel6.1, 6.1, 6.1
LinuxLinux22e9947a4b2ba255888541bd0111cf00b9b16586, 22e9947a4b2ba255888541bd0111cf00b9b16586, 22e9947a4b2ba255888541bd0111cf00b9b16586

Timeline

  • Aug 10, 2026 CVE Published
  • Aug 11, 2026 Coalition ESS Score
  • Aug 16, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (8 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-68147
vulnetix vdb fixes CVE-2026-68147

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-68147/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›