CVE-2026-89723nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 14, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 36a580eb489f54d81a0534974962e732a314b999 before 39005fd1ce654ffdecacddc406b9a038efe606e6; from 36a580eb489f54d81a0534974962e732a314b999 before bf49e6f6ddc12445a0330708b365de6458085980; 36a580eb489f54d81a0534974962e732a314b999 builds before 4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d; from 36a580eb489f54d81a0534974962e732a314b999 before b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf; 36a580eb489f54d81a0534974962e732a314b999 builds before 5d3783c451a546373662ee11ec17019273e68034; from 36a580eb489f54d81a0534974962e732a314b999 before 448636c745a3f3b8582a0b8ce718c890a11c0fa9; from 36a580eb489f54d81a0534974962e732a314b999 before 28362e8ce51377afdec1782e661e808328a10514; from 36a580eb489f54d81a0534974962e732a314b999 before 45662dedb8f272ef7f16e69f13424c4bd0399240 | CNA record |
References
- https://git.kernel.org/stable/c/39005fd1ce654ffdecacddc406b9a038efe606e6
- https://git.kernel.org/stable/c/bf49e6f6ddc12445a0330708b365de6458085980
- https://git.kernel.org/stable/c/4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d
- https://git.kernel.org/stable/c/b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf
- https://git.kernel.org/stable/c/5d3783c451a546373662ee11ec17019273e68034
- https://git.kernel.org/stable/c/448636c745a3f3b8582a0b8ce718c890a11c0fa9
- https://git.kernel.org/stable/c/28362e8ce51377afdec1782e661e808328a10514
- https://git.kernel.org/stable/c/45662dedb8f272ef7f16e69f13424c4bd0399240
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.