nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 28362e8ce51377afdec1782e661e808328a10514, Kernel 39005fd1ce654ffdecacddc406b9a038efe606e6, Kernel 448636c745a3f3b8582a0b8ce718c890a11c0fa9 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation Shuangpeng Bai reported that KASAN detected a slab-out-of-bounds error in nilfs_direct_propagate() during testing. Analysis revealed that after truncating a file, a node block immediately below the B-tree root was not deleted. Instead, it remained in the B-tree node cache in a dirty state. The log writer subsequently detected this block and incorrectly invoked nilfs_direct_propagate() on it, which is designed to handle only data blocks in direct mapping. B-tree nodes in the cache are managed by virtual block numbers, and their logical keys typically exceed the range expected by direct mapping. Consequently, processing such a node as a direct mapping entry triggers a slab-out-of-bounds access. The root cause is that when a B-tree mapping collapses into a direct mapping during truncation, an intermediate node block pointed to by the root node is left behind as garbage instead of being explicitly deleted. This resolves the issue by adding a nilfs_btree_discard() operation to delete the remaining intermediate node block during the conversion. A 'deform' flag is added to the bop_delete interface to explicitly signal that the deletion is part of a mapping transformation. This allows the B-tree mapping implementation to perform the necessary cleanup and discarding of the residual node structure that would be otherwise be left orphaned after the transition.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.30, >=36a580eb489f54d81a0534974962e732a314b999 <28362e8ce51377afdec1782e661e808328a10514, >=36a580eb489f54d81a0534974962e732a314b999 <39005fd1ce654ffdecacddc406b9a038efe606e6, >=36a580eb489f54d81a0534974962e732a314b999 <448636c745a3f3b8582a0b8ce718c890a11c0fa9, >=36a580eb489f54d81a0534974962e732a314b999 <45662dedb8f272ef7f16e69f13424c4bd0399240, >=36a580eb489f54d81a0534974962e732a314b999 <4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d, >=36a580eb489f54d81a0534974962e732a314b999 <5d3783c451a546373662ee11ec17019273e68034, >=36a580eb489f54d81a0534974962e732a314b999 <b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf, >=36a580eb489f54d81a0534974962e732a314b999 <bf49e6f6ddc12445a0330708b365de6458085980 | 28362e8ce51377afdec1782e661e808328a10514, 39005fd1ce654ffdecacddc406b9a038efe606e6, 448636c745a3f3b8582a0b8ce718c890a11c0fa9, 45662dedb8f272ef7f16e69f13424c4bd0399240, 4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d, 5d3783c451a546373662ee11ec17019273e68034, b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf, bf49e6f6ddc12445a0330708b365de6458085980 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket