CVE-2026-89723

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

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:46 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.3036a580eb489f54d81a0534974962e732a314b999
Vendor states this is fixed in 28362e8ce51377afdec1782e661e808328a10514 (fixed)
Vendor states this is fixed in 39005fd1ce654ffdecacddc406b9a038efe606e6 (fixed)
Vendor states this is fixed in 448636c745a3f3b8582a0b8ce718c890a11c0fa9 (fixed)
Vendor states this is fixed in 45662dedb8f272ef7f16e69f13424c4bd0399240 (fixed)
Vendor states this is fixed in 4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d (fixed)
Vendor states this is fixed in 5d3783c451a546373662ee11ec17019273e68034 (fixed)
Vendor states this is fixed in b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf (fixed)
Vendor states this is fixed in bf49e6f6ddc12445a0330708b365de6458085980 (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card