SECUFOCUSNOW
Home›CVE index›CVE-2025-40084
Review reviewHigh

CVE-2025-40084

Linux

In the Linux kernel, the following vulnerability has been resolved: ksmbd: transport_ipc: validate payload size before reading handle handle_response() dereferences the payload as a 4-byte handle without verifying that the declared payload size is at least 4 bytes. A malformed or truncated message from ksmbd.mountd can lead to a 4-byte read past the declared payload size. Validate the size before dereferencing. This is a minimal fix to guard the initial handle read.

CVSS
7.1
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.10.29
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.1

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ksmbd: transport_ipc: validate payload size before reading handle handle_response() dereferences the payload as a 4-byte handle without verifying that the declared payload size is at least 4 bytes. A malformed or truncated message from ksmbd.mountd can lead to a 4-byte read past the declared payload size. Validate the size before dereferencing. This is a minimal fix to guard the initial handle read.

Affected product and versions

Product
Linux
Affected versions
>= 0626e6641f6b467447c81dd7678a69c66f7746cf < a02e432d5130da4c723aabe1205bac805889fdb2, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 2dc125f5da134c0915a840b62565c60a595673dd, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 898d527ed94c19980a4d848f10057f1fed578ffb, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 867ffd9d67285612da3f0498ca618297f8e41f01, >= 0626e6641f6b467447c81dd7678a69c66f7746cf < 6f40e50ceb99fc8ef37e5c56e2ec1d162733fef0, >= 5.15
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux 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:N/A:H
CWE
Not available