Kernel memory disclosure via wrapped SMB response bounds
Published Aug 15, 2026 · Updated Aug 15, 2026
Out-of-bounds read in the Linux kernel SMB client allows remote attackers controlling an SMB server to disclose kernel memory. The smb2_ioctl_query_info() bounds check adds two untrusted 32-bit response fields directly, allowing OutputOffset plus the requested length to wrap before comparison. Reachability requires the client to process a crafted passthrough FSCTL response from a malicious SMB server; copy_to_user() then exposes data beyond the response buffer to userspace.
Summary
What happened
Out-of-bounds read in the Linux kernel SMB client allows remote attackers controlling an SMB server to disclose kernel memory. The smb2_ioctl_query_info() bounds check adds two untrusted 32-bit response fields directly, allowing OutputOffset plus the requested length to wrap before comparison. Reachability requires the client to process a crafted passthrough FSCTL response from a malicious SMB server; copy_to_user() then exposes data beyond the response buffer to userspace.
The record
- CVE
- CVE-2026-72310
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=2005c32ec99ee2490e8131b3953f3f212009ffea
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <160045fc943f6c46b227644261252c8a22b8a87a
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <1627e7d5c9b09721a141d07cedb178882f1ded67
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <175357ee0c596cb82054650dfa32fda51ad35aaa
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <1a638c55f2db6cb2296e5e3138015dd8fd9d4aa9
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <63feb687e89a3a52a31e6e01764117cc500f1974
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <a4f27ad055392fa164f5649e89a3637b033c5fcc
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <b30771b69eafae750afb7385fbcc3d77ed3f3670
- Affected versionversion=2b1116bbe898aefdf584838448c6869f69851e0f <dbd126539c098dba3159ce7d34b10b2daddcbd0f
- Affected versionversion=5.4.69 <5.5
- Affected versionversion=5.5
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo