{"id":5353,"date":"2026-09-04T18:47:46","date_gmt":"2026-09-04T10:47:46","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-68147"},"modified":"2026-09-04T18:47:46","modified_gmt":"2026-09-04T10:47:46","slug":"cve-2026-68147","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-68147","title":{"rendered":"CVE-2026-68147 [HIGH] &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nfscrypt: Avoid dynami"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>fscrypt: Avoid dynamic allocation in fscrypt_get_devices()<\/p>\n<p>When a blk_crypto_key starts being used or is evicted, fs\/crypto\/ calls<br \/>\nfscrypt_get_devices() to get the filesystem&#8217;s list of block devices,<br \/>\nthen iterates over them and calls blk_crypto_config_supported(),<br \/>\nblk_crypto_start_using_key(), or blk_crypto_evict_key() on each one.<\/p>\n<p>Currently, the block device pointers are placed in a dynamically<br \/>\nallocated array.  This dynamic allocation is problematic because:<\/p>\n<p>&#8211; It can fail, especially at the fscrypt_destroy_inline_crypt_key() call<br \/>\n  site when it&#8217;s invoked for inode eviction under direct reclaim.<\/p>\n<p>&#8211; fscrypt_destroy_inline_crypt_key() doesn&#8217;t handle the failure.  It<br \/>\n  just zeroizes and frees the blk_crypto_key without calling<br \/>\n  blk_crypto_evict_key().  That causes a use-after-free.<\/p>\n<p>For now, let&#8217;s fix this in the straightforward and easily-backportable<br \/>\nway by switching to an on-stack array.  Currently the fscrypt<br \/>\nmulti-device functionality is used only by f2fs, which has a hardcoded<br \/>\nlimit of 8 block devices.  An on-stack array works fine for that.<\/p>\n<p>(Of course, this solution won&#8217;t scale up to large number of block<br \/>\ndevices.  For that we&#8217;d need a different solution, like moving the block<br \/>\ndevice iteration into the filesystem.  Or in the case of btrfs, which<br \/>\nwill only support blk-crypto-fallback, we should make it just call<br \/>\nblk-crypto-fallback directly, so the block devices won&#8217;t be needed.)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>fscrypt: Avoid dynamic allocation in fscrypt_get_devices()<\/p>\n<p>When a blk_crypto_key starts being used or is evicted, fs\/crypto\/ calls<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-5353","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/5353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}