Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Nov 12, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2025-40123

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.158-16.1.158-1
Debian:13linuxbefore 6.12.57-16.12.57-1
Debian:14linuxbefore 6.17.6-16.17.6-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.9.1.160000.2.66.12.0-160000.9.1.160000.2.6
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-symsbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.9.16.12.0-160000.9.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.9.16.12.0-160000.9.1

+4

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • 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 mapping
    0Monitor
  • ← EarlierCVE-2025-40122Nov 12, 2025 · perf/x86/intel: Fix IA32_PMC_x_CFG_B MSRs access error
    0Monitor
  • Later →CVE-2025-40124Nov 12, 2025 · sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux08cb3dc9d2b44f153d0bcf2cb966e4a94b5d0f32Vendor (CNA)
Linux Linux4540aed51b12bc13364149bf95f6ecef013197c0Vendor (CNA)
Linux Linuxa99de19128aec0913f3d529f529fbbff5edfaff8Vendor (CNA)
Linux Linuxc1ad19b5d8e23123503dcaf2d4342e1b90b923adVendor (CNA)
Linux Linuxdc4f348952173beb8ceb15be30b249276eccb605Vendor (CNA)
Linux Linuxe53a59e7cee5c1605d1ed595933098c2b69108f9Vendor (CNA)
Linux Linuxf856c598080ba7ce1252867b8ecd6ad5bdaf9a6aVendor (CNA)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.9.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.9.1.160000.2.6 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.9.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.9.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.9.1 · SUSE:Linux Micro 6.2Package 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.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-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.

  1. Published
  2. First PoC+285 d
  3. 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.

Finders, 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

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records