Answer in brief
CVE-2026-98168 records a Unknown severity vulnerability in smb: client: fix reparse buffer bounds in cifs_query_reparse_point(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=48ca7139ab7f0bbed95ff7a901ea497017769657 <3d67f155fe5813cfb02a551a9a12d6ea06a902e9 || >=56e84c64fc257a95728ee73165456b025c48d408 <d1152c96a3002e3df6b9a5b007cecaa7b19b4f79 || >=56e84c64fc257a95728ee73165456b025c48d408 <8dc5db3a0e583ea8d31d0613cefd99e93e095c3c || >=56e84c64fc257a95728ee73165456b025c48d408 <5f0306e731e2f46e91419eae57eee3a241c055e0 || 848d78e3625f15de09d34a562dc49a98b78a62f3 || c13b779d26b3702fba8f7d5fe757aba5bda85fd0 || >=6.12.34 <6.12.112 || >=6.6.94 <6.7 || >=6.15.3 <6.16 | 3d67f155fe5813cfb02a551a9a12d6ea06a902e9, d1152c96a3002e3df6b9a5b007cecaa7b19b4f79, 8dc5db3a0e583ea8d31d0613cefd99e93e095c3c, 5f0306e731e2f46e91419eae57eee3a241c055e0, 6.12.112, 6.7, 6.16 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix reparse buffer bounds in cifs_query_reparse_point() In cifs_query_reparse_point(), the start >= end check before casting to struct reparse_data_buffer * only ensures the start pointer is within the response. It fails to verify that there is enough space remaining for the fixed 8-byte header of the structure. If a server provides a DataOffset that leaves less than 8 bytes remaining, the check passes, but subsequent reads of ReparseTag and ReparseDataLength will occur out-of-bounds. Fix this by ensuring the remaining space is at least the size of the reparse_data_buffer structure before accessing its fields.
Quoted source text, attributed separately from HOL analysis.