CVE-2026-89632
Last modified
CVE-2026-89632 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr() reparse_buf_ptr() reads buf->ReparseDataLength before checking that count covers the full fixed header: buf = (struct reparse_data_buffer *)((u8 *)io + off); len = sizeof(*buf); /* 8 bytes */ rdlen = le16_to_cpu(buf->ReparseDataLength); /* offset 4, 2 bytes */ if (count < len || count < rdlen + len) /* check comes after */ struct reparse_data_buffer has ReparseDataLength at offset 4. If a server returns OutputCount < 6, the read at offset 4-5 reaches past the end of the received data. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr() reparse_buf_ptr() reads buf->ReparseDataLength before checking that count covers the full fixed header: buf = (struct reparse_data_buffer *)((u8 *)io + off); len = sizeof(*buf); /* 8 bytes */ rdlen = le16_to_cpu(buf->ReparseDataLength); /* offset 4, 2 bytes */ if (count < len || count < rdlen + len) /* check comes after */ struct reparse_data_buffer has ReparseDataLength at offset 4. If a server returns OutputCount < 6, the read at offset 4-5 reaches past the end of the received data. The off+count bounds against iov_len were already validated, but that does not protect against count being smaller than sizeof(*buf). Split the check: verify count >= sizeof(*buf) before reading ReparseDataLength, then verify count covers the data region.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a158bb66b1373866d9fd5997565a58a573085539, < 711cf71300d7992f450600df8864917d3538679f; >= a158bb66b1373866d9fd5997565a58a573085539, < 05f78e6cf34ea3a285053bd5999e08e8ac298bd5 |
| Linux | Linux | >= 6.6.32, < 7.2.4; >= 6.6.32, < 7.3-rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89632?
How severe is CVE-2026-89632?
How do I fix CVE-2026-89632?
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-89627In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89628In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89629In the Linux kernel, the following vulnerability has been re…
- CVE-2026-8963Spoofing issue in the Web Speech component. This vulnerabili…7.5
- CVE-2026-89630In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-89631In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-89633In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89634In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-89635In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89636In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89637In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89638In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-89632?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
