Kernel memory disclosure via unchecked SMB2 WRITE length
Published Dec 23, 2022 · Updated Apr 14, 2025
Out-of-bounds read in Linux kernel ksmbd 5.15 through 5.18 before 5.18.18 allows remote authenticated users to read kernel memory. In smb2_write, the non-padding path accepts an SMB2 WRITE DataOffset and Length without checking that their sum stays within the received request buffer. A valid SMB session and writable share are required; the over-read can disclose kernel memory or crash the host.
Summary
What happened
Out-of-bounds read in Linux kernel ksmbd 5.15 through 5.18 before 5.18.18 allows remote authenticated users to read kernel memory. In smb2_write, the non-padding path accepts an SMB2 WRITE DataOffset and Length without checking that their sum stays within the received request buffer. A valid SMB session and writable share are required; the over-read can disclose kernel memory or crash the host.
The record
- CVE
- CVE-2022-47940
- Published
- Dec 23, 2022
- Updated
- Apr 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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