Answer in brief
CVE-2026-98318 records a Unknown severity vulnerability in smb: client: validate absolute native symlink targets before NT fixups. 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 | >=3363da82e02f1bddc54faa92ea430c6532e2cd2e <6913ff607c2bc8694193e1fcc40bf16d75f35f16 || >=3363da82e02f1bddc54faa92ea430c6532e2cd2e <23c240d9509e15f72e4112fc95f0160ab32ec430 || b6ea7b6c6be65149ab6b8e37a9dd1671f76add1b || >=6.15.6 <6.16 | 6913ff607c2bc8694193e1fcc40bf16d75f35f16, 23c240d9509e15f72e4112fc95f0160ab32ec430, 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: validate absolute native symlink targets before NT fixups With symlinkroot unset, an absolute target is copied without conversion to an NT drive path. Later code still assumes an NT prefix is present when modifying the target and calculating the print name length. For "/ab", this causes two failures: sym[5] and path[5] are written past their allocations, and plen -= 2 * poff subtracts an assumed 8-byte prefix from a 6-byte UTF-16 target, wrapping u16 plen to 65534. That underflow causes another overflow: memcpy() copies 65534 bytes into a 24-byte buffer. A user with write access to a mounted share can trigger these bugs with default settings. Validate the NT drive prefix, including an ASCII drive letter, before accessing fixed offsets or subtracting the prefix length.
Quoted source text, attributed separately from HOL analysis.