CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32, 4540aed51b12bc13364149bf95f6ecef013197c0, a99de19128aec0913f3d529f529fbbff5edfaff8.
Low priority for now. Upgrade to Linux Linux 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32, 4540aed51b12bc13364149bf95f6ecef013197c0, a99de19128aec0913f3d529f529fbbff5edfaff8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.17affected
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before e53a59e7cee5c1605d1ed595933098c2b69108f9affected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before dc4f348952173beb8ceb15be30b249276eccb605affected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before a99de19128aec0913f3d529f529fbbff5edfaff8affected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32affected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before f856c598080ba7ce1252867b8ecd6ad5bdaf9a6aaffected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before c1ad19b5d8e23123503dcaf2d4342e1b90b923adaffected · git
- 5e43f899b03a3492ce5fc44e8900becb04dae9c0 and later · before 4540aed51b12bc13364149bf95f6ecef013197c0affected · git
- before 4.17not affected · semver
- 5.10.270 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.9.1.160000.2.6 | 6.12.0-160000.9.1.160000.2.6 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-azure | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-docs | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-kvmsmall | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-obs-qa | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-syms | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Enterprise Server 16.0 | kernel-zfcpdump | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.9.1 | 6.12.0-160000.9.1 |
+4
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40121Nov 12, 2025 · ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping0Monitor
- ← EarlierCVE-2025-40122Nov 12, 2025 · perf/x86/intel: Fix IA32_PMC_x_CFG_B MSRs access error0Monitor
- Later →CVE-2025-40124Nov 12, 2025 · sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32 | Vendor (CNA) |
| Linux Linux | 4540aed51b12bc13364149bf95f6ecef013197c0 | Vendor (CNA) |
| Linux Linux | a99de19128aec0913f3d529f529fbbff5edfaff8 | Vendor (CNA) |
| Linux Linux | c1ad19b5d8e23123503dcaf2d4342e1b90b923ad | Vendor (CNA) |
| Linux Linux | dc4f348952173beb8ceb15be30b249276eccb605 | Vendor (CNA) |
| Linux Linux | e53a59e7cee5c1605d1ed595933098c2b69108f9 | Vendor (CNA) |
| Linux Linux | f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.9.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-azure | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-docs | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-kvmsmall | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-obs-qa | 6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.9.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
+2
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-24 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+285 d
- TodayNov 7, 2026+360 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/4540aed51b12bc13364149bf95f6ecef013197c0
- git.kernel.org/stable/c/a99de19128aec0913f3d529f529fbbff5edfaff8
- git.kernel.org/stable/c/c1ad19b5d8e23123503dcaf2d4342e1b90b923ad
- git.kernel.org/stable/c/dc4f348952173beb8ceb15be30b249276eccb605
- git.kernel.org/stable/c/e53a59e7cee5c1605d1ed595933098c2b69108f9
- git.kernel.org/stable/c/f856c598080ba7ce1252867b8ecd6ad5bdaf9a6a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.