CVE-2024-50163: Linux kernel · bpf: Make sure internal and UAPI
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1080.87~20.04.1 : update Linux kernel when convenient.
Data as of 29 Oct 2026, 22:34 UTC
- Patch
- Available – fixed in 5.15.0-1080.87~20.04.1, 5.15.0-1081.90~20.04.1, 5.15.0-1077.86~20.04.1 +62
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Make sure internal and UAPI bpf_redirect flags don't overlap The bpf_redirect_info is shared between the SKB and XDP redirect paths, and the two paths use the same numeric flag values in the ri->flags field (specifically, BPF_F_BROADCAST == BPF_F_NEXTHOP). This means that if skb bpf_redirect_neigh() is used with a non-NULL params argument and, subsequently, an XDP redirect is performed using the same bpf_redirect_info struct, the XDP path will get confused and end up crashing, which syzbot managed to trigger. With the stack-allocated bpf_redirect_info, the structure is no longer shared between the SKB and XDP paths, so the crash doesn't happen anymore. However, different code paths using identically-numbered flag values in the same struct field still seems like a bit of a mess, so this patch cleans that up by moving the flag definitions together and redefining the three flags in BPF_F_REDIRECT_INTERNAL to not overlap with the flags used for XDP. It also adds a BUILD_BUG_ON() check to make sure the overlap is not re-introduced by mistake.
References
- ubuntu.com/security/CVE-2024-50163 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-50163 (opens in a new tab)
- git.kernel.org/linus/09d88791c7cd888d5195c84733caf9183dcfbd16 (opens in a new tab)
- git.kernel.org/stable/c/4e1e428533845d48828bd3875c0e92e8565b9962 (opens in a new tab)
- git.kernel.org/stable/c/314dbee9fe4f5cee36435465de52c988d7caa466 (opens in a new tab)
- git.kernel.org/stable/c/0fca5ed4be8e8bfbfb9bd97845af596bab7192d3 (opens in a new tab)
- git.kernel.org/stable/c/cec288e05ceac9a0d3a3a1fd279534b11844c826 (opens in a new tab)
- git.kernel.org/stable/c/09d88791c7cd888d5195c84733caf9183dcfbd16 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7291-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7288-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7305-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7289-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7308-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7310-1 (opens in a new tab)