Vulnerability · Published Oct 21, 2024 · Assigned by Linux

CVE-2024-50063bpf: Prevent tail call between progs attached to different hooks

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 14% 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 85.6% 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: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.135-1DSA-5907-1
Debian:12linux6.1.135-1DEBIAN-CVE-2024-50063
Debian:13linux6.11.4-1DEBIAN-CVE-2024-50063
Debian:14linux6.11.4-1DEBIAN-CVE-2024-50063
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux6.8.0-56.58USN-7383-1
Ubuntu:24.04:LTSlinux6.8.0-56.58UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-aws6.8.0-1025.27UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-aws6.8.0-1025.27USN-7383-1
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1027.29~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-azure6.8.0-1025.30UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1012.12~24.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1025.30~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1014.15UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gcp6.8.0-1026.28UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gcp6.8.0-1026.28USN-7383-1
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1011.11~24.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1026.28~22.04.1USN-7383-1
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1026.28~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gke6.8.0-1021.25UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gke6.8.0-1021.25USN-7383-1
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1008.10UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1008.10USN-7383-1
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-57.59~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-ibm6.8.0-1022.22UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1023.23~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-56.58.1USN-7383-1
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-56.58.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-56.58.1~22.04.1USN-7383-1
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-56.58.1~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1024.27UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1024.27USN-7383-1
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1007.7UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1024.27~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1024.27~22.04.1USN-7383-1
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1024.27.1UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1024.27.1USN-7383-1
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1004.4UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1015.15UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-oem-6.86.8.0-1024.24UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-oracle6.8.0-1022.23UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-oracle6.8.0-1022.23USN-7383-1
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1022.23~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1022.23~22.04.1USN-7383-1
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-raspi6.8.0-1028.32UBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-riscv6.8.0-56.58.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-56.58.1~22.04.1UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-50063
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1017.18UBUNTU-CVE-2024-50063
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2024-50063

Affected products (as reported)

VendorProductVersions
Linux Linux f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 – before d9a807fb7cbfad4328824186e2e4bee28f72169bf1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 – before 5d5e3b4cbe8ee16b7bf96fd73a421c92a9da3ca1f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 – before 88c2a10e6c176c2860cd0659f4c0e9d20b3f64d1f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6 – before 28ead3eaabc16ecc907cfb71876da028080f6356
Linux Linux 5.5

References