CVE-2026-72210: ntfs: fix off-by-one in mapping pairs decoding bounds checks

Published Aug 15, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ntfs: fix off-by-one in mapping pairs decoding bounds checks

In ntfsmappingpairsdecompress(), attrend points one byte past the end of the attribute record:

attrend = (u8 )attr + le32tocpu(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 attrend:

b = buf & 0xf; if (b) { if (unlikely(buf + b > attrend)) // off-by-one goto ioerror; for (deltaxcn = (s8)buf[b--]; b; b--) deltaxcn = (deltaxcn << 8) + buf[b]; }

When buf + b == attrend, 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 attrend is correctly rejected as out of bounds.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In ntfs_mapping_pairs_decompress(), change the bounds checks for mapping pair data bytes to use >= instead of > so that when buf + b == attr_end the access is allowed (and buf[b] at exactly attr_end is not rejected/treated as out-of-bounds). Specifically address the off-by-one in checks like 'if (unlikely(buf + b > attr_end))' to become '>=', and apply the same >= pattern to the related LCN delta bytes check.

    Linux kernel (ntfs mapping pairs decoding) mapping pairs bounds checks = >= (change strict > to non-strict >=)

Event History

Aug 15, 2026
CVE Published
via MITRE·05:54 AM
Data Sourced
via MITRE·05:54 AM
DescriptionSeverity
Data Sourced
via NVD·06:21 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-72210?

CVE-2026-72210 has a risk rating of 17, indicating a significant vulnerability in the Linux kernel.

2

How do I fix CVE-2026-72210?

To fix CVE-2026-72210, ensure that you update your Linux kernel to the latest version that addresses this vulnerability.

3

What systems are affected by CVE-2026-72210?

CVE-2026-72210 affects systems utilizing the NTFS file system within the Linux kernel.

4

What type of vulnerability is CVE-2026-72210?

CVE-2026-72210 is an off-by-one vulnerability that occurs during the decoding of mapping pairs in the NTFS file system.

5

When was CVE-2026-72210 published?

CVE-2026-72210 was published on August 15, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203