fs/ntfs3: validate ef->size covers the record's name and value
Noroxi assessment
Priority: Monitor (action score 36/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.69% (FIRST EPSS); higher than 51.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 077df8464cf24f8ffc82fb6efec2ae600686e699, 28a924c7e67e6d71abeb04860b61166fecb027fc, 5.15.221; 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 077df8464cf24f8ffc82fb6efec2ae600686e699, 28a924c7e67e6d71abeb04860b61166fecb027fc, 5.15.221; 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
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate ef->size covers the record's name and value When an EA record has a non-zero ef->size, ntfs_read_ea() only checks that the record fits in the remaining buffer (ea_size > bytes), not that ef->size is large enough to hold the record's own name_len + 1 + elength. A crafted image can pass validation with, e.g., ef->size = 24 but elength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of the undersized record, reading past the kmalloc(info->size) allocation and leaking heap memory to userspace via getxattr(): BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302) Read of size 65535 at addr ffff888100794550 by task exploit __asan_memcpy (mm/kasan/shadow.c:105) ntfs_get_ea (fs/ntfs3/xattr.c:302) ntfs_getxattr (fs/ntfs3/xattr.c:848) __vfs_getxattr (fs/xattr.c:441) vfs_getxattr (fs/xattr.c:474) do_getxattr (fs/xattr.c:800) path_getxattrat (fs/xattr.c:868) do_syscall_64 (arch/x86/entry/syscall_64.c:94) The buggy address is located 80 bytes inside of allocated 84-byte region in cache kmalloc-96 Compute the size the record needs and require ef->size to cover it.
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.7% · 52th percentile
- CWE
- —
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.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
- 6.2affected
- 333feb7ba84f69f9b423422417aaac54fd9e7c84 and later · before b27e68ad818a4ca2cef8f35f97e75d756714c818affected · git
- 000a9a72efa4a9df289bab9c9e8ba1639c72e0d6 and later · before 28a924c7e67e6d71abeb04860b61166fecb027fcaffected · git
- 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b and later · before d585ed08308909c7e6fefb4e8a258aeb29b19ff9affected · git
- 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b and later · before 077df8464cf24f8ffc82fb6efec2ae600686e699affected · git
- 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b and later · before aab1880058ac767d3ea9388a9a7221c776c22c44affected · git
- 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b and later · before c8a109c9e23a2c7fd548473dde728b2cb8188146affected · git
- 0e8235d28f3a0e9eda9f02ff67ee566d5f42b66b and later · before c22f91d82cb9a29d22bdffdce6c803467984ad0caffected · git
- 5.15.121 and later · before 5.15.221affected · semver
- 6.1.40 and later · before 6.1.188affected · 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 | all versions | — |
| 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 077df8464cf24f8ffc82fb6efec2ae600686e699 | Vendor (CNA) |
| Linux Linux | 28a924c7e67e6d71abeb04860b61166fecb027fc | Vendor (CNA) |
| Linux Linux | 5.15.221 | Vendor (CNA) |
| Linux Linux | 6.1.188 | Vendor (CNA) |
| Linux Linux | aab1880058ac767d3ea9388a9a7221c776c22c44 | Vendor (CNA) |
| Linux Linux | b27e68ad818a4ca2cef8f35f97e75d756714c818 | Vendor (CNA) |
| Linux Linux | c22f91d82cb9a29d22bdffdce6c803467984ad0c | Vendor (CNA) |
| Linux Linux | c8a109c9e23a2c7fd548473dde728b2cb8188146 | Vendor (CNA) |
| Linux Linux | d585ed08308909c7e6fefb4e8a258aeb29b19ff9 | 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.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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 (6 more)Show less
- git.kernel.org/stable/c/28a924c7e67e6d71abeb04860b61166fecb027fc
- git.kernel.org/stable/c/aab1880058ac767d3ea9388a9a7221c776c22c44
- git.kernel.org/stable/c/b27e68ad818a4ca2cef8f35f97e75d756714c818
- git.kernel.org/stable/c/c22f91d82cb9a29d22bdffdce6c803467984ad0c
- git.kernel.org/stable/c/c8a109c9e23a2c7fd548473dde728b2cb8188146
- git.kernel.org/stable/c/d585ed08308909c7e6fefb4e8a258aeb29b19ff9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.