CVE-2024-50163
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2024
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
bpf: Make sure internal and UAPI bpf_redirect flags don't overlap
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| e624d4ed4aa8cc3c69d1359b0aaea539203ed266 | affected | git | 4e1e428533845d48828bd3875c0e92e8565b9962 | Unavailable | None listed |
| e624d4ed4aa8cc3c69d1359b0aaea539203ed266 | affected | git | 314dbee9fe4f5cee36435465de52c988d7caa466 | Unavailable | None listed |
| e624d4ed4aa8cc3c69d1359b0aaea539203ed266 | affected | git | 0fca5ed4be8e8bfbfb9bd97845af596bab7192d3 | Unavailable | None listed |
| e624d4ed4aa8cc3c69d1359b0aaea539203ed266 | affected | git | cec288e05ceac9a0d3a3a1fd279534b11844c826 | Unavailable | None listed |
| e624d4ed4aa8cc3c69d1359b0aaea539203ed266 | affected | git | 09d88791c7cd888d5195c84733caf9183dcfbd16 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.14 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.14 | Unavailable | None listed |
| 5.15.170 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.1.115 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.59 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.11.6 | unaffected | semver | Unavailable | 6.11.* | None listed |
| 6.12 | unaffected | original_commit_for_fix | Unavailable | * | None listed |