CVE-2026-97437: ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e()
Noroxi assessment
Priority: Monitor (action score 28/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0505f1e7bb5b981b6ed62d98b26ddce76142865d, 2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2ba, 6a8149a20e46086c756c2a9202e377c0b649a0c3.
Low priority for now. Upgrade to Linux Linux 0505f1e7bb5b981b6ed62d98b26ddce76142865d, 2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2ba, 6a8149a20e46086c756c2a9202e377c0b649a0c3 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: ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e() The bounds check in ntfs_dir_emit() compares fname->name_len (a character count) against e->size (a byte count) without accounting for the 2-byte-per-character UTF-16LE encoding or the ATTR_FILE_NAME header size: if (fname->name_len + sizeof(struct NTFS_DE) > le16_to_cpu(e->size)) This computes: name_len + 16 > e_size The correct check must account for the ATTR_FILE_NAME header (66 bytes before the name) and the UTF-16LE character size (2 bytes each): sizeof(NTFS_DE) + offsetof(ATTR_FILE_NAME, name) + name_len * sizeof(short) > e_size Which computes: 16 + 66 + name_len * 2 > e_size The correct calculation already exists as fname_full_size() in ntfs.h and is used in cmp_fnames(), namei.c, and fslog.c, but was not used in the readdir path. A crafted NTFS image with an index entry containing a small e->size but large fname->name_len bypasses the current check, causing ntfs_utf16_to_nls() to read past the entry boundary. Additionally, add a key_size validation in hdr_find_e() to ensure the declared key_size does not exceed the available entry data, preventing comparison functions from reading past entry boundaries on the lookup path.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before d1f98938e437732c0ecdfc8ee451e12a072f6d07affected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 0505f1e7bb5b981b6ed62d98b26ddce76142865daffected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2baaffected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before ed6da1abeec50db9060d714f03743fe0b63e4fe4affected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before 6a8149a20e46086c756c2a9202e377c0b649a0c3affected · git
- 4342306f0f0d5ff4315a204d315c1b51b914fca5 and later · before aa1bdbb39f49c5bc9779316891c40005517842a5affected · git
- before 5.15not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
- 6.1.189 and later · up to and including 6.1.*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-97435Sep 24, 2026 · net: dsa: sja1105: flower: reject cross-chip redirect0Monitor
- ← EarlierCVE-2026-97436Sep 24, 2026 · dpaa2-switch: rework FDB management on the bridge leave path0Monitor
- Later →CVE-2026-97438Sep 24, 2026 · fs/ntfs3: validate index entry key bounds28Monitor
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 | 0505f1e7bb5b981b6ed62d98b26ddce76142865d | Vendor (CNA) |
| Linux Linux | 2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2ba | Vendor (CNA) |
| Linux Linux | 6a8149a20e46086c756c2a9202e377c0b649a0c3 | Vendor (CNA) |
| Linux Linux | aa1bdbb39f49c5bc9779316891c40005517842a5 | Vendor (CNA) |
| Linux Linux | d1f98938e437732c0ecdfc8ee451e12a072f6d07 | Vendor (CNA) |
| Linux Linux | ed6da1abeec50db9060d714f03743fe0b63e4fe4 | Vendor (CNA) |
| 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
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
nvd-secondary
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 (5 more)Show less
- git.kernel.org/stable/c/2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2ba
- git.kernel.org/stable/c/6a8149a20e46086c756c2a9202e377c0b649a0c3
- git.kernel.org/stable/c/aa1bdbb39f49c5bc9779316891c40005517842a5
- git.kernel.org/stable/c/d1f98938e437732c0ecdfc8ee451e12a072f6d07
- git.kernel.org/stable/c/ed6da1abeec50db9060d714f03743fe0b63e4fe4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.