CVE-2026-89723

nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation

State
Published
Severity
7.8 High
Published
Sep 11, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 36a580eb489f54d81a0534974962e732a314b999 to before 39005fd1ce654ffdecacddc406b9a038efe606e6Affected
  • 36a580eb489f54d81a0534974962e732a314b999 to before bf49e6f6ddc12445a0330708b365de6458085980Affected
  • 36a580eb489f54d81a0534974962e732a314b999 to before 4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826dAffected
  • 36a580eb489f54d81a0534974962e732a314b999 to before b313edfbc0c2a60f7ce09b2e81ee71909ab8ddafAffected
  • 36a580eb489f54d81a0534974962e732a314b999 to before 5d3783c451a546373662ee11ec17019273e68034Affected
  • 36a580eb489f54d81a0534974962e732a314b999 to before 448636c745a3f3b8582a0b8ce718c890a11c0fa9Affected
  • 36a580eb489f54d81a0534974962e732a314b999 to before 28362e8ce51377afdec1782e661e808328a10514Affected
  • 36a580eb489f54d81a0534974962e732a314b999 to before 45662dedb8f272ef7f16e69f13424c4bd0399240Affected
LinuxLinux
  • 2.6.30Affected
  • before 2.6.30Not affected
  • 5.10.270 through 5.10.*Not affected
  • 5.15.221 through 5.15.*Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.109 through 6.12.*Not affected
  • 6.18.50 through 6.18.*Not affected
  • 7.2.4 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.