CVE-2026-31433: ksmbd: fix potencial OOB in get_file_all_info() for compound requests

Published Apr 22, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix potencial OOB in getfileallinfo() for compound requests

When a compound request consists of QUERYDIRECTORY + QUERYINFO (FILEALLINFORMATION) and the first command consumes nearly the entire maxtranssize, getfileallinfo() would blindly call smbConvertToUTF16() with PATHMAX, causing out-of-bounds write beyond the response buffer. In getfileallinfo(), there was a missing validation check for the client-provided OutputBufferLength before copying the filename into FileName field of the smb2fileallinfo structure. If the filename length exceeds the available buffer space, it could lead to potential buffer overflows or memory corruption during smbConvertToUTF16 conversion. This calculating the actual free buffer size using smb2calcmaxoutbuflen() and returning -EINVAL if the buffer is insufficient and updating smbConvertToUTF16 to use the actual filename length (clamped by PATHMAX) to ensure a safe copy operation.

Affected Software

12 affected components
Linux ksmbd (Linux kernel)
Linux Linux kernel>=5.15.145<5.15.203
Linux Linux kernel>=6.1.71<6.1.168
Linux Linux kernel>=6.6<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Linux kernel ksmbd to a version that resolves this vulnerability.

    Patch ksmbd: fix potencial OOB in get_file_all_info() for compound requests

Event History

Apr 22, 2026
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-31433?

CVE-2026-31433 is categorized with a medium severity level due to its potential to cause an out-of-bounds access.

2

How do I fix CVE-2026-31433?

To fix CVE-2026-31433, update your Linux kernel to the latest version where this vulnerability has been addressed.

3

What impact does CVE-2026-31433 have on systems?

CVE-2026-31433 could allow remote attackers to exploit out-of-bounds access, potentially leading to denial of service or information disclosure.

4

Which versions of ksmbd are affected by CVE-2026-31433?

CVE-2026-31433 affects ksmbd implemented in the Linux kernel prior to the patch release that addresses this vulnerability.

5

Is CVE-2026-31433 exploitable in a production environment?

Yes, if not mitigated, CVE-2026-31433 could be exploited in a production environment, posing a security risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203