Review reviewHigh

CVE-2025-40123

Linux

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_...

CVSS
7.8
EPSS
0.15%
4.74% percentile
CISA KEV
Not listed
Published
2025.11.12
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce expected_attach_type for tailcall compatibility Yinhao et al. recently reported: Our fuzzer tool discovered an uninitialized pointer issue in the bpf_prog_test_run_xdp() function within the Linux kernel's BPF subsystem. This leads to a NULL pointer dereference when a BPF program attempts to deference the txq member of struct xdp_buff object. The test initializes two programs of BPF_PROG_TYPE_XDP: progA acts as the entry point for bpf_prog_test_run_xdp() and its expected_attach_type can neither be of be BPF_XDP_...

Affected product and versions

Product
Linux
Affected versions
>= 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < a99de19128aec0913f3d529f529fbbff5edfaff8, >= 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32, >= 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a, >= 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < c1ad19b5d8e23123503dcaf2d4342e1b90b923ad, >= 5e43f899b03a3492ce5fc44e8900becb04dae9c0 < 4540aed51b12bc13364149bf95f6ecef013197c0, >= 4.17
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:H/A:H
CWE
Not available