CVE-2026-72470: fs/ntfs3: resize log->one_page_buf when adopting on-disk page size
Noroxi assessment
Priority: Monitor (action score 31/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.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374, 220a6ef5e89a11ffd5e490046b86dc9fb6da0e4b, 4f129fc6f756f8541e5bff45b1804cc11b1ec712.
Low priority for now. Upgrade to Linux Linux 2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374, 220a6ef5e89a11ffd5e490046b86dc9fb6da0e4b, 4f129fc6f756f8541e5bff45b1804cc11b1ec712 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: resize log->one_page_buf when adopting on-disk page size log_replay() allocates log->one_page_buf using the page size that was chosen from the host PAGE_SIZE: log->one_page_buf = kmalloc(log->page_size, GFP_NOFS); Later, when a restart area is found, the log page size recorded on disk is adopted: t32 = le32_to_cpu(log->rst_info.r_page->sys_page_size); if (log->page_size != t32) { log->l_size = log->orig_file_size; log->page_size = norm_file_page(t32, &log->l_size, t32 == DefaultLogPageSize); } If the on-disk page size is larger than the size used for the initial allocation, log->page_size grows but one_page_buf is left at its original, smaller size. A subsequent unaligned read_log_page() then reads log->page_size bytes into the undersized scratch buffer: page_buf = page_off ? log->one_page_buf : *buffer; err = ntfs_read_run_nb_ra(ni->mi.sbi, &ni->file.run, page_vbo, page_buf, log->page_size, NULL, &log->read_ahead); overflowing the allocation. This is reachable when mounting a dirty NTFS volume whose log was formatted with a page size larger than the buffer initially allocated on the mounting host (for example a 64K-log volume mounted on a host that allocated a 4K scratch buffer). Grow one_page_buf when the adopted on-disk page size exceeds the size used for the initial allocation. On krealloc() failure the original buffer is left intact and freed by the existing error path.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- 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.
Is your version affected? Check itNoroxi 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
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before 220a6ef5e89a11ffd5e490046b86dc9fb6da0e4baffected · git
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before 2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374affected · git
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before f1422df595d69b997d23a8f11e12c528ccef7fadaffected · git
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before 4f129fc6f756f8541e5bff45b1804cc11b1ec712affected · git
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before c99444f6dfca893f6d310aae4a53c620f98f7b4faffected · git
- b46acd6a6a627d876898e1c84d3f84902264b445 and later · before 5a35454179fe1041d9cd286f5d320ce0d448c12aaffected · git
- before 5.15not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*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 | from 0 | — |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72466Aug 15, 2026 · xprtrdma: Fix bcall rep leak and unbounded peek39Monitor
- ← EarlierCVE-2026-72469Aug 15, 2026 · xprtrdma: Fix ep kref imbalance on ADDR_CHANGE35Monitor
- Later →CVE-2026-72472Aug 15, 2026 · nfs: use nfsi->rwsem to protect traversal of the file lock list39Monitor
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 | 2097a2537d9d1c29c0e20ed0dbf717a0ccd8f374 | Vendor (CNA) |
| Linux Linux | 220a6ef5e89a11ffd5e490046b86dc9fb6da0e4b | Vendor (CNA) |
| Linux Linux | 4f129fc6f756f8541e5bff45b1804cc11b1ec712 | Vendor (CNA) |
| Linux Linux | 5a35454179fe1041d9cd286f5d320ce0d448c12a | Vendor (CNA) |
| Linux Linux | c99444f6dfca893f6d310aae4a53c620f98f7b4f | Vendor (CNA) |
| Linux Linux | f1422df595d69b997d23a8f11e12c528ccef7fad | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/220a6ef5e89a11ffd5e490046b86dc9fb6da0e4b
- git.kernel.org/stable/c/4f129fc6f756f8541e5bff45b1804cc11b1ec712
- git.kernel.org/stable/c/5a35454179fe1041d9cd286f5d320ce0d448c12a
- git.kernel.org/stable/c/c99444f6dfca893f6d310aae4a53c620f98f7b4f
- git.kernel.org/stable/c/f1422df595d69b997d23a8f11e12c528ccef7fad
Vendor advisories and official records. Exploit/PoC links are deliberately left out.