cve.bz

CVE-2025-40123 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.270
  • Linux Linux: fixed in 5.15.221
  • Linux Linux: fixed in 6.1.156
  • Linux Linux: fixed in 6.6.112
  • Linux Linux: fixed in 6.12.53
  • Linux Linux: fixed in 6.17.3
  • Linux Linux: fixed in 6.18
  • Debian, Ubuntu, SUSE, openSUSE, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2025-40123 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-40123?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-40123?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-40123 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.17 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.270
Linux5.155.15.221
Linux6.16.1.156
Linux6.66.6.112
Linux6.126.12.53
Linux6.176.17.3
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux-6.16.1.158-1~deb11u1DLA-4379-1
Debian12linux6.1.158-1DEBIAN-CVE-2025-40123
Debian13linux6.12.57-1DEBIAN-CVE-2025-40123
Debian14linux6.17.6-1DEBIAN-CVE-2025-40123
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-40123
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-40123
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-40123
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2025-40123 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2025-40123 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1050.53~22.04.1UBUNTU-CVE-2025-40123 USN-8095-4
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2025-40123 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-40123 USN-8126-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2025-40123 USN-8962-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-40123
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2025-40123 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-40123 USN-8095-1
75 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.9.1SUSE-SU-2026:20228-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.290.1SUSE-SU-2026:0316-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_761-8.7.1SUSE-SU-2026:0316-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_81-150700.1.3.1SUSE-SU-2026:0278-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_81-150700.15.3.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.28.1.150700.17.19.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150700.53.28.1SUSE-SU-2026:0315-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150700.20.24.1SUSE-SU-2026:0281-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.290.1SUSE-SU-2026:0316-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.9.1SUSE-SU-2026:20220-1
11 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6openSUSE-SU-2026:20145-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.9.1openSUSE-SU-2026:20145-1
Alpaquita23linux-lts6.1.156-r0BELL-CVE-2025-40123
Alpaquita25linux-lts6.12.53-r0BELL-CVE-2025-40123
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-40123

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

BPF programs specify expected_attach_type to enable attach-point-specific functionality beyond the base prog_type. For XDP, BPF_XDP_DEVMAP programs can access xdp_md's egress_ifindex field, while regular XDP programs cannot. For CGROUP_SOCK_ADDR, different attach types permit different helper functions like bpf_bind. Tailcalls allow one program to jump to another, but the compatibility check only verified prog_type matches—not expected_attach_type. An attacker creates progA (e.g., regular XDP) that tailcalls into progB (e.g., XDP_DEVMAP), which then accesses fields or calls helpers it shouldn't have permission to use, causing crashes or uninitialized pointer accesses. The fix enforces expected_attach_type matching for tailcall maps.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-40123.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON