SECUFOCUSNOW
Home›CVE index›CVE-2024-26936
Review reviewHigh

CVE-2024-26936

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate request buffer size in smb2_allocate_rsp_buf() The response buffer should be allocated in smb2_allocate_rsp_buf before validating request. But the fields in payload as well as smb2 header is used in smb2_allocate_rsp_buf(). This patch add simple buffer size validation to avoid potencial out-of-bounds in request buffer.

CVSS
7.8
EPSS
0.60%
45.4% percentile
CISA KEV
Not listed
Published
2024.05.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.60%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate request buffer size in smb2_allocate_rsp_buf() The response buffer should be allocated in smb2_allocate_rsp_buf before validating request. But the fields in payload as well as smb2 header is used in smb2_allocate_rsp_buf(). This patch add simple buffer size validation to avoid potencial out-of-bounds in request buffer.

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 0626e6641f6b467447c81dd7678a69c66f7746cf < 8f3d0bf1d0c62b539d54c5b9108a845cff619b99, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 21ff9d7d223c5c19cb4334009e4c0c83a2f4d674, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 5c20b242d4fed73a93591e48bfd9772e2322fb11, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 2c27a64a2bc47d9bfc7c3cf8be14be53b1ee7cb6, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 17cf0c2794bdb6f39671265aa18aea5c22ee8c4a, >= 5.15, >= 5.15 < 5.15.159, >= 5.16 < 6.1.88, >= 6.2 < 6.6.29, >= 6.7 < 6.8.8, 6.9
Fixed versions
5.15.159, 6.1.88, 6.6.29, 6.8.8

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-120