Skip to main content
VulnerabilityPublished Updated

CVE-2026-98171: Linux kernel · smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-98171· High 8.8

Not known to be exploited · CVSS 8.8 High · fixed in 8749946579708ea0d339034bb7f423a67dbe89cf : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.18.8
Patch
Available – fixed in 8749946579708ea0d339034bb7f423a67dbe89cf, 05762c5bc1cfdcac36747994fde2c04387a457f1, 858d5ac22cb889266993e7670f9f0c4f4aeedd78 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 8749946579708ea0d339034bb7f423a67dbe89cf
Fixed in
  • 8749946579708ea0d339034bb7f423a67dbe89cf
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 05762c5bc1cfdcac36747994fde2c04387a457f1
Fixed in
  • 05762c5bc1cfdcac36747994fde2c04387a457f1
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 858d5ac22cb889266993e7670f9f0c4f4aeedd78
Fixed in
  • 858d5ac22cb889266993e7670f9f0c4f4aeedd78
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 491e33144dee872cffda207f6fcb09260728f803
Fixed in
  • 491e33144dee872cffda207f6fcb09260728f803
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 96c436e4b010711452b2872558938f4ef276492a
Fixed in
  • 96c436e4b010711452b2872558938f4ef276492a
LinuxLinuxAffected
  • ≥ b24df3e30cbf48255db866720fb71f14bf9d2f39, < 72eaef1f37a3b6bec11c342736834dc3707be3e4
Fixed in
  • 72eaef1f37a3b6bec11c342736834dc3707be3e4

Description

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.

References

Community reviews

Loading reviews…