Answer in brief
CVE-2026-98171 records a Unknown severity vulnerability in smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs. 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 | >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <72eaef1f37a3b6bec11c342736834dc3707be3e4 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <491e33144dee872cffda207f6fcb09260728f803 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <8749946579708ea0d339034bb7f423a67dbe89cf || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <96c436e4b010711452b2872558938f4ef276492a || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <858d5ac22cb889266993e7670f9f0c4f4aeedd78 || >=b24df3e30cbf48255db866720fb71f14bf9d2f39 <05762c5bc1cfdcac36747994fde2c04387a457f1 | 72eaef1f37a3b6bec11c342736834dc3707be3e4, 491e33144dee872cffda207f6fcb09260728f803, 8749946579708ea0d339034bb7f423a67dbe89cf, 96c436e4b010711452b2872558938f4ef276492a, 858d5ac22cb889266993e7670f9f0c4f4aeedd78, 05762c5bc1cfdcac36747994fde2c04387a457f1 |
| Linux/Linuxgeneric | 4.19 | 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 next_buffer UAF and NextCommand bounds in compound PDUs Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames: - Clear next_buffer after assigning it to server->bigbuf. A stale next_buffer pointer can lead to a use-after-free on subsequent error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using the pre-decryption length allows NextCommand to point into stale ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the trailing slice is large enough for a header.
Quoted source text, attributed separately from HOL analysis.