Invalid client memory access via malformed SMB responses
Published Oct 6, 2026 · Updated Oct 6, 2026
Linux SMB client flaws allow remote attackers controlling an SMB server to trigger invalid memory access via encrypted compound responses. In receive_encrypted_standard(), a stale next_buffer survives transfer to server->bigbuf, while NextCommand validation uses the pre-decryption length and permits short or overflowing offsets. The client must process an encrypted compound response from a malicious or compromised SMB server; the published fix identifies use-after-free and out-of-bounds reads, not code execution.
Summary
What happened
Linux SMB client flaws allow remote attackers controlling an SMB server to trigger invalid memory access via encrypted compound responses. In receive_encrypted_standard(), a stale next_buffer survives transfer to server->bigbuf, while NextCommand validation uses the pre-decryption length and permits short or overflowing offsets. The client must process an encrypted compound response from a malicious or compromised SMB server; the published fix identifies use-after-free and out-of-bounds reads, not code execution.
The record
- CVE
- CVE-2026-98171
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.19
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <05762c5bc1cfdcac36747994fde2c04387a457f1
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <491e33144dee872cffda207f6fcb09260728f803
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <72eaef1f37a3b6bec11c342736834dc3707be3e4
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <858d5ac22cb889266993e7670f9f0c4f4aeedd78
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <8749946579708ea0d339034bb7f423a67dbe89cf
- Affected versionversion=b24df3e30cbf48255db866720fb71f14bf9d2f39 <96c436e4b010711452b2872558938f4ef276492a
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started