CVE-2026-97437
Last modified
CVE-2026-97437 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < d1f98938e437732c0ecdfc8ee451e12a072f6d07; >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < 0505f1e7bb5b981b6ed62d98b26ddce76142865d; >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < 2f7d0ec8c10dc7bf7a8c9a9cb169f9a4d1fac2ba; >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < ed6da1abeec50db9060d714f03743fe0b63e4fe4; >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < 6a8149a20e46086c756c2a9202e377c0b649a0c3; >= 4342306f0f0d5ff4315a204d315c1b51b914fca5, < aa1bdbb39f49c5bc9779316891c40005517842a5 |
| Linux | Linux | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97437?
How severe is CVE-2026-97437?
How do I fix CVE-2026-97437?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97431In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97432In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97433In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-97434In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97435In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97436In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97438In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-97439In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9744IBM Netezza Software 11.3.0.3 through Interim Fix 002 does n…5.9
- CVE-2026-97440In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97441In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97442In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-97437?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
