nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 39005fd1ce654ffdecacddc406b9a038efe606e6; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in bf49e6f6ddc12445a0330708b365de6458085980; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 5d3783c451a546373662ee11ec17019273e68034; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 448636c745a3f3b8582a0b8ce718c890a11c0fa9; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 28362e8ce51377afdec1782e661e808328a10514; From 36a580eb489f54d81a0534974962e732a314b999 · fixed in 45662dedb8f272ef7f16e69f13424c4bd0399240
- Linux Linux
2.6.30
- KernelLinux
From 2.6.30 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/39005fd1ce654ffdecacddc406b9a038efe606e6
- stable/c/bf49e6f6ddc12445a0330708b365de6458085980
- stable/c/4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d
- stable/c/b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf
- stable/c/5d3783c451a546373662ee11ec17019273e68034
- stable/c/448636c745a3f3b8582a0b8ce718c890a11c0fa9
- stable/c/28362e8ce51377afdec1782e661e808328a10514
- stable/c/45662dedb8f272ef7f16e69f13424c4bd0399240