CVE-2026-89785: fs/ntfs3: fix out-of-bounds read of INDEX_ROOT in reparse/objid init
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 2064bc663f89e61b8681c1fb9d1ce445de72063d, 64bb6000bfbdf241a6dd578199acd90321a4243e, 66c074eab6f966fbe48a0fc4b3a45b2a2e2df527; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 2064bc663f89e61b8681c1fb9d1ce445de72063d, 64bb6000bfbdf241a6dd578199acd90321a4243e, 66c074eab6f966fbe48a0fc4b3a45b2a2e2df527; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix out-of-bounds read of INDEX_ROOT in reparse/objid init ntfs_reparse_init() and ntfs_objid_init() parse the index root of the $Extend/$Reparse and $Extend/$ObjId metafiles (the INDEX_ROOT attributes named $R and $O). They read its type and rule fields through resident_data(), which does not check that the resident attribute is large enough to hold them. mi_enum_attr() accepts a resident attribute with data_off == asize and data_size == 0. For such an attribute placed last in its MFT record, resident_data() returns a pointer to the end of the record_size buffer, so reading root->type / root->rule reads past the allocation. Use resident_data_ex(attr, sizeof(struct INDEX_ROOT)) and bail out when it returns NULL, as ntfs_security_init() already does for $SDH / $SII. The attribute is only parsed while mounting a crafted image, so this needs CAP_SYS_ADMIN. BUG: KASAN: slab-out-of-bounds in ntfs_reparse_init (fs/ntfs3/fsntfs.c:2306) Read of size 4 at addr ffff88801219dc00 by task mount ntfs_reparse_init (fs/ntfs3/fsntfs.c:2306) ntfs_fill_super (fs/ntfs3/super.c:1604) get_tree_bdev_flags (fs/super.c:1703) vfs_get_tree (fs/super.c:1758) path_mount (fs/namespace.c:4131) __x64_sys_mount (fs/namespace.c:4360)
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before eb80003744e32a7366a523015e4acfe0a2ac7d88affected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before bd631e2005290a55c8edda87363bc0d594c01705affected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before 94fce1d3e74fe011e21f17490ba58491709fd7e5affected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before 66c074eab6f966fbe48a0fc4b3a45b2a2e2df527affected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before 64bb6000bfbdf241a6dd578199acd90321a4243eaffected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before 72caafbc95c5dca8266a942b8e96ad81d8d9adc7affected · git
- 82cae269cfa953032fbb8980a7d554d60fb00b17 and later · before 2064bc663f89e61b8681c1fb9d1ce445de72063daffected · git
- before 5.15not affected · semver
- 5.15.221 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89783Sep 16, 2026 · xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full39Monitor
- ← EarlierCVE-2026-89784Sep 16, 2026 · SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/60Monitor
- Later →CVE-2026-89786Sep 16, 2026 · ext4: fix out-of-bounds read in ext4_read_inline_dir()36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2064bc663f89e61b8681c1fb9d1ce445de72063d | Vendor (CNA) |
| Linux Linux | 64bb6000bfbdf241a6dd578199acd90321a4243e | Vendor (CNA) |
| Linux Linux | 66c074eab6f966fbe48a0fc4b3a45b2a2e2df527 | Vendor (CNA) |
| Linux Linux | 72caafbc95c5dca8266a942b8e96ad81d8d9adc7 | Vendor (CNA) |
| Linux Linux | 94fce1d3e74fe011e21f17490ba58491709fd7e5 | Vendor (CNA) |
| Linux Linux | bd631e2005290a55c8edda87363bc0d594c01705 | Vendor (CNA) |
| Linux Linux | eb80003744e32a7366a523015e4acfe0a2ac7d88 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/64bb6000bfbdf241a6dd578199acd90321a4243e
- git.kernel.org/stable/c/66c074eab6f966fbe48a0fc4b3a45b2a2e2df527
- git.kernel.org/stable/c/72caafbc95c5dca8266a942b8e96ad81d8d9adc7
- git.kernel.org/stable/c/94fce1d3e74fe011e21f17490ba58491709fd7e5
- git.kernel.org/stable/c/bd631e2005290a55c8edda87363bc0d594c01705
- git.kernel.org/stable/c/eb80003744e32a7366a523015e4acfe0a2ac7d88
Vendor advisories and official records. Exploit/PoC links are deliberately left out.