CVE-2026-89723

Out-of-bounds access via stale B-tree node propagation

Published Sep 11, 2026 · Updated Sep 11, 2026

Out-of-bounds memory access in Linux nilfs2 from 2.6.30 allows local users to fault the kernel by truncating a file on a mounted NILFS2 volume. During B-tree-to-direct-map collapse, truncation leaves an intermediate node dirty in the cache, and the log writer passes it to nilfs_direct_propagate as a data block. The path requires write access to a mounted NILFS2 file; KASAN observed an invalid slab access, with no reported code execution or data disclosure.

CVSS severityUnavailable
Unscored
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Out-of-bounds memory access in Linux nilfs2 from 2.6.30 allows local users to fault the kernel by truncating a file on a mounted NILFS2 volume. During B-tree-to-direct-map collapse, truncation leaves an intermediate node dirty in the cache, and the log writer passes it to nilfs_direct_propagate as a data block. The path requires write access to a mounted NILFS2 file; KASAN observed an invalid slab access, with no reported code execution or data disclosure.

The record

CVE
CVE-2026-89723
Published
Sep 11, 2026
Updated
Sep 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 11, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.30
  2. Affected versionversion=36a580eb489f54d81a0534974962e732a314b999 <28362e8ce51377afdec1782e661e808328a10514
  3. Affected versionversion=36a580eb489f54d81a0534974962e732a314b999 <448636c745a3f3b8582a0b8ce718c890a11c0fa9
  4. Affected versionversion=36a580eb489f54d81a0534974962e732a314b999 <45662dedb8f272ef7f16e69f13424c4bd0399240
  5. Affected versionversion=36a580eb489f54d81a0534974962e732a314b999 <5d3783c451a546373662ee11ec17019273e68034

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=2.6.30; version=36a580eb489f54d81a0534974962e732a314b999 <28362e8ce51377afdec1782e661e808328a10514; version=36a580eb489f54d81a0534974962e732a314b999 <448636c745a3f3b8582a0b8ce718c890a11c0fa9; version=36a580eb489f54d81a0534974962e732a314b999 <45662dedb8f272ef7f16e69f13424c4bd0399240; version=36a580eb489f54d81a0534974962e732a314b999 <5d3783c451a546373662ee11ec17019273e68034

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo