Vulnerability · Published May 5, 2025 · Assigned by Linux

CVE-2024-58098bpf: track changes_pkt_data property for global functions

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 9% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 90.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: bpf: track changes_pkt_data property for global functions When processing calls to certain helpers, verifier invalidates all packet pointers in a current state. For example, consider the following program: __attribute__((__noinline__)) long skb_pull_data(struct __sk_buff *sk, __u32 len) { return bpf_skb_pull_data(sk, len); } SEC("tc") int test_invalidate_checks(struct __sk_buff *sk) { int *p = (void *)(long)sk->data; if ((void *)(p + 1) > (void *)(long)sk->data_end) return TCX_DROP; skb_pull_data(sk, 0); *p = 42; return TCX_PASS; } After a call to bpf_skb_pull_data() the pointer 'p' can't be used safely. See function filter.c:bpf_helper_changes_pkt_data() for a list of such helpers. At the moment verifier invalidates packet pointers when processing helper function calls, and does not traverse global sub-programs when processing calls to global sub-programs. This means that calls to helpers done from global sub-programs do not invalidate pointers in the caller state. E.g. the program above is unsafe, but is not rejected by verifier. This commit fixes the omission by computing field bpf_subprog_info->changes_pkt_data for each sub-program before main verification pass. changes_pkt_data should be set if: - subprogram calls helper for which bpf_helper_changes_pkt_data returns true; - subprogram calls a global function, for which bpf_subprog_info->changes_pkt_data should be set. The verifier.c:check_cfg() pass is modified to compute this information. The commit relies on depth first instruction traversal done by check_cfg() and absence of recursive function calls: - check_cfg() would eventually visit every call to subprogram S in a state when S is fully explored; - when S is fully explored: - every direct helper call within S is explored (and thus changes_pkt_data is set if needed); - every call to subprogram S1 called by S was visited with S1 fully explored (and thus S inherits changes_pkt_data from S1). The downside of such approach is that dead code elimination is not taken into account: if a helper call inside global function is dead because of current configuration, verifier would conservatively assume that the call occurs for the purpose of the changes_pkt_data computation.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2024-58098
Debian:13linux6.12.25-1DEBIAN-CVE-2024-58098
Debian:14linux6.12.25-1DEBIAN-CVE-2024-58098
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1035.38USN-8781-1
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2024-58098
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2024-58098
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2024-58098

Affected products (as reported)

VendorProductVersions
Linux Linux 51c39bb1d5d105a02e29aa7960f0a395086e6342 – before 79751e9227a5910c0e5a2c7186877d91821d957d51c39bb1d5d105a02e29aa7960f0a395086e6342 – before 1d572c60488b52882b719ed273767ee3b280413d51c39bb1d5d105a02e29aa7960f0a395086e6342 – before 51081a3f25c742da5a659d7fc6fd77ebfdd555be
Linux Linux 5.6

References