In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In… (CVE-2026-72210)
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In ntfs_mapping_pairs_decompress(), attr_end points one byte past the end of the attribute record: attr_end = (u8 *)attr + le32_to_cpu(attr->length); The two bounds checks validating that mapping pair data bytes fit within the attribute use strict greater-than (>), which allows a one-byte out-of-bounds read when the data extends exactly to attr_end: b = *buf & 0xf; if (b) { if (unlikely(buf + b > attr_end)) // off-by-one goto io_error; for (deltaxcn = (s8)buf[b--]; b; b--) deltaxcn = (deltaxcn << 8) + buf[b]; } When buf + b == attr_end, the check evaluates to false and buf[b] reads one byte past the valid attribute boundary. The same pattern appears in the LCN delta bytes check. Fix both checks to use >= so that buf[b] at exactly attr_end is correctly rejected as out of bounds.
AI Analysis
Technical Summary
The Linux kernel's ntfs_mapping_pairs_decompress() function contained an off-by-one error in its bounds checks for mapping pair data bytes. Specifically, the code used strict greater-than (>) comparisons to validate that buffer accesses did not exceed the attribute record boundary, allowing a read of one byte past the valid memory when the buffer end equaled the attribute end. This was corrected by changing the checks to use greater-than-or-equal (>=), ensuring that any attempt to read exactly at the boundary is correctly rejected, preventing out-of-bounds reads.
Potential Impact
This vulnerability could lead to a one-byte out-of-bounds read in kernel memory when processing NTFS attributes. While the impact details such as privilege escalation or denial of service are not provided, out-of-bounds reads can potentially cause system instability or information disclosure depending on context. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the off-by-one error by adjusting the bounds checks. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed in the provided data; check the vendor's advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In… (CVE-2026-72210)
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In ntfs_mapping_pairs_decompress(), attr_end points one byte past the end of the attribute record: attr_end = (u8 *)attr + le32_to_cpu(attr->length); The two bounds checks validating that mapping pair data bytes fit within the attribute use strict greater-than (>), which allows a one-byte out-of-bounds read when the data extends exactly to attr_end: b = *buf & 0xf; if (b) { if (unlikely(buf + b > attr_end)) // off-by-one goto io_error; for (deltaxcn = (s8)buf[b--]; b; b--) deltaxcn = (deltaxcn << 8) + buf[b]; } When buf + b == attr_end, the check evaluates to false and buf[b] reads one byte past the valid attribute boundary. The same pattern appears in the LCN delta bytes check. Fix both checks to use >= so that buf[b] at exactly attr_end is correctly rejected as out of bounds.
CVSS v3.1
Score 9.8critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's ntfs_mapping_pairs_decompress() function contained an off-by-one error in its bounds checks for mapping pair data bytes. Specifically, the code used strict greater-than (>) comparisons to validate that buffer accesses did not exceed the attribute record boundary, allowing a read of one byte past the valid memory when the buffer end equaled the attribute end. This was corrected by changing the checks to use greater-than-or-equal (>=), ensuring that any attempt to read exactly at the boundary is correctly rejected, preventing out-of-bounds reads.
Potential Impact
This vulnerability could lead to a one-byte out-of-bounds read in kernel memory when processing NTFS attributes. While the impact details such as privilege escalation or denial of service are not provided, out-of-bounds reads can potentially cause system instability or information disclosure depending on context. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the off-by-one error by adjusting the bounds checks. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed in the provided data; check the vendor's advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-hpv2-jq93-768m
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72210"]
Threat ID: 6a808b73bf8831d5394fe125
Added to database: 08/15/2026, 15:53:23 UTC
Last enriched: 08/15/2026, 16:47:56 UTC
Last updated: 09/30/2026, 06:54:40 UTC
Views: 47
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.