Kernel memory fault via ext4 inline directory
Published Sep 16, 2026 · Updated Sep 16, 2026
Out-of-bounds read in Linux ext4 directory iteration allows attackers to trigger a kernel memory fault via a crafted inline directory. ext4_read_inline_dir() calculates positions in a logical space larger than its allocated inline buffer and dereferences a directory-entry header before confirming that the header fits. Reaching the flaw requires the kernel to read a crafted or corrupted inline ext4 directory; the demonstrated consequence is a memory-safety fault during getdents64(), while data disclosure has not been established.
Summary
What happened
Out-of-bounds read in Linux ext4 directory iteration allows attackers to trigger a kernel memory fault via a crafted inline directory. ext4_read_inline_dir() calculates positions in a logical space larger than its allocated inline buffer and dereferences a directory-entry header before confirming that the header fits. Reaching the flaw requires the kernel to read a crafted or corrupted inline ext4 directory; the demonstrated consequence is a memory-safety fault during getdents64(), while data disclosure has not been established.
The record
- CVE
- CVE-2026-89786
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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.
- Affected versionversion=3.10
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <1a1dea633b724a1c042dbcdb1fed27f410916688
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <36bf17bb90cdf7a623499b624b05acde4d2feef5
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <5fd20d4e50dd6e460b3ea8e4396f8553d4526f8f
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <6702c7da86d8cdb88d0fc57166286e115ffeb8c0
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <9333cc809f0a89e001b814155a6cb8903a6274df
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <b060861f662d4826dc700a1c3584243bb3474cfe
- Affected versionversion=c4d8b0235aa98f8c26bf94d308be3fdd24154572 <d1e7c186555ad65554fd2f2b02f5a539aa35ae48
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- syzkaller ext4_read_inline_dir C reproducerproof of concept · demonstrated
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