SMB2 response miscalculation via hardcoded buffer offsets
Published Apr 22, 2026 · Updated Apr 22, 2026
Response-size miscalculation in Linux Kernel ksmbd allows remote attackers to trigger incorrect SMB2 buffer sizing via crafted requests. The smb2_query_dir, smb2_get_ea, get_file_stream_info, and smb2_ioctl paths pass hardcoded header lengths to smb2_calc_max_out_buf_len instead of each response structure's Buffer offset. The ksmbd server must be enabled and reachable; the upstream record does not disclose whether exploitation causes a crash, memory disclosure, or code execution.
Summary
What happened
Response-size miscalculation in Linux Kernel ksmbd allows remote attackers to trigger incorrect SMB2 buffer sizing via crafted requests. The smb2_query_dir, smb2_get_ea, get_file_stream_info, and smb2_ioctl paths pass hardcoded header lengths to smb2_calc_max_out_buf_len instead of each response structure's Buffer offset. The ksmbd server must be enabled and reachable; the upstream record does not disclose whether exploitation causes a crash, memory disclosure, or code execution.
The record
- CVE
- CVE-2026-31478
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=6.6
- Affected versionversion=9f297df20d93411c0b4ddad7f88ba04a7cd36e77 <9a7166f0ef8cbb7bb48dd05e2471d995566003f5
- Affected versionversion=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <0e55f63dd08f09651d39e1b709a91705a8a0ddcb
- Affected versionversion=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <4cb537ae4f37d7d0f617815ed4bed7173fb50861
- Affected versionversion=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <6aef1765d6807e0f027cd87f6ac973eb0879a46d
- Affected versionversion=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <80824c7e527b70cf9039534e60aff592e8f209d1
- Affected versionversion=e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d <c3a89e3ec1ccf64fa6a34e391e1581ebbcba8683
- Affected versionversion=f2283680a80571ca82d710bc6ecd8f8beac67d63 <70b4c414889492c522b6e4331562360f49be2361
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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