Answer in brief
CVE-2026-89632 records a High severity (CVSS 8.2) vulnerability in smb: client: fix use-before-check of ReparseDataLength in reparse_buf_ptr(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a158bb66b1373866d9fd5997565a58a573085539 <711cf71300d7992f450600df8864917d3538679f || >=a158bb66b1373866d9fd5997565a58a573085539 <05f78e6cf34ea3a285053bd5999e08e8ac298bd5 | 711cf71300d7992f450600df8864917d3538679f, 05f78e6cf34ea3a285053bd5999e08e8ac298bd5 |
| Linux/Linuxgeneric | >=6.6.32 <7.2.4 || >=6.6.32 <7.3-rc1 | 7.2.4, 7.3-rc1 |
| Linux/Linuxgeneric | >=6.6.32 <7.2.4 || >=6.6.32 <7.3 | 7.2.4, 7.3 |
| Linux/Linuxgeneric | >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <711cf71300d7992f450600df8864917d3538679f || >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <05f78e6cf34ea3a285053bd5999e08e8ac298bd5 || a158bb66b1373866d9fd5997565a58a573085539 || >=6.6.32 <6.7 | 711cf71300d7992f450600df8864917d3538679f, 05f78e6cf34ea3a285053bd5999e08e8ac298bd5, 6.7 |
| Linux/Linuxgeneric | 6.8 | Not reported |
| Linux/Linuxgeneric | >=a158bb66b1373866d9fd5997565a58a573085539 <b70bc592afd19732e2e4563300ebe8f974280365 || >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <711cf71300d7992f450600df8864917d3538679f || >=67ec9949b0dfe78c99e110dd975eb7dc5645630c <05f78e6cf34ea3a285053bd5999e08e8ac298bd5 || >=6.6.32 <6.6.160 | b70bc592afd19732e2e4563300ebe8f974280365, 711cf71300d7992f450600df8864917d3538679f, 05f78e6cf34ea3a285053bd5999e08e8ac298bd5, 6.6.160 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.