CVE-2025-40123bpf: Enforce expected_attach_type for tailcall compatibility
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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_DEVMAP nor BPF_XDP_CPUMAP. progA calls into a slot of a tailcall map it owns. progB's expected_attach_type must be BPF_XDP_DEVMAP to pass xdp_is_valid_access() validation. The program returns struct xdp_md's egress_ifindex, and the latter is only allowed to be accessed under mentioned expected_attach_type. progB is then inserted into the tailcall which progA calls. The underlying issue goes beyond XDP though. Another example are programs of type BPF_PROG_TYPE_CGROUP_SOCK_ADDR. sock_addr_is_valid_access() as well as sock_addr_func_proto() have different logic depending on the programs' expected_attach_type. Similarly, a program attached to BPF_CGROUP_INET4_GETPEERNAME should not be allowed doing a tailcall into a program which calls bpf_bind() out of BPF which is only enabled for BPF_CGROUP_INET4_CONNECT. In short, specifying expected_attach_type allows to open up additional functionality or restrictions beyond what the basic bpf_prog_type enables. The use of tailcalls must not violate these constraints. Fix it by enforcing expected_attach_type in __bpf_prog_map_compatible(). Note that we only enforce this for tailcall maps, but not for BPF devmaps or cpumaps: There, the programs are invoked through dev_map_bpf_prog_run*() and cpu_map_bpf_prog_run*() which set up a new environment / context and therefore these situations are not prone to this issue.
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < e53a59e7cee5c1605d1ed595933098c2b69108f9
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < dc4f348952173beb8ceb15be30b249276eccb605
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < a99de19128aec0913f3d529f529fbbff5edfaff8
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < c1ad19b5d8e23123503dcaf2d4342e1b90b923ad
- affected 5e43f899b03a3492ce5fc44e8900becb04dae9c0 – < 4540aed51b12bc13364149bf95f6ecef013197c0
- affected 4.17
- unaffected < 4.17
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.156 – ≤ 6.1.*
- unaffected 6.6.112 – ≤ 6.6.*
- unaffected 6.12.53 – ≤ 6.12.*
- unaffected 6.17.3 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References7
- https://git.kernel.org/stable/c/e53a59e7cee5c1605d1ed595933098c2b69108f9 (opens in a new tab)
- https://git.kernel.org/stable/c/dc4f348952173beb8ceb15be30b249276eccb605 (opens in a new tab)
- https://git.kernel.org/stable/c/a99de19128aec0913f3d529f529fbbff5edfaff8 (opens in a new tab)
- https://git.kernel.org/stable/c/08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32 (opens in a new tab)
- https://git.kernel.org/stable/c/f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a (opens in a new tab)
- https://git.kernel.org/stable/c/c1ad19b5d8e23123503dcaf2d4342e1b90b923ad (opens in a new tab)
- https://git.kernel.org/stable/c/4540aed51b12bc13364149bf95f6ecef013197c0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-124960 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40123)Record last updated .