CVE-2024-27050

libbpf: Use OPTS_SET() macro in bpf_xdp_query()

HIGH
7.8
CVSS Score
Published: May 1, 2024 at 12:54 PM UTC
Updated: August 5, 2026 at 12:04 PM UTC
2 products affected across 1 vendorLinux KernelAcrn

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: libbpf: Use OPTS_SET() macro in bpf_xdp_query() When the feature_flags and xdp_zc_max_segs fields were added to the libbpf bpf_xdp_query_opts, the code writing them did not use the OPTS_SET() macro. This causes libbpf to write to those fields unconditionally, which means that programs compiled against an older version of libbpf (with a smaller size of the bpf_xdp_query_opts struct) will have its stack corrupted by libbpf writing out of bounds. The patch adding the feature_flags field has an early bail out if the feature_flags field is not part of the opts struct (via the OPTS_HAS) macro, but the patch adding xdp_zc_max_segs does not. For consistency, this fix just changes the assignments to both fields to use the OPTS_SET() macro.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
Vendor states this is fixed in 6.8.2 (unaffected)
6.6 ≤ v < 6.6.236.6 ≤ v < 6.7.116.6 ≤ v < 6.8.26.6 ≤ v < 6.96.7 ≤ v < 6.7.116.8 ≤ v < 6.8.213ce2daa259a3bfbc9a5aeeee8b9a870587037316.6
Vendor states this is fixed in 682ddd62abd4bdcee7584246903e7a2df005fe0d (fixed)
Vendor states this is fixed in 92a871ab9fa59a74d013bc04f321026a057618e7 (fixed)
Vendor states this is fixed in cd3be9843247edb8fc6fcd8d8237cbce2bc19f5e (fixed)
Vendor states this is fixed in fa5bef5e80c6a3321b2b1a7070436f3bc5daf07c (fixed)
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.23 (unaffected)
Vendor states this is fixed in 6.7.11 (unaffected)
Vendor states this is fixed in 6.8.2 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/682ddd62abd4bdcee7584246903e7a2df005fe0d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/92a871ab9fa59a74d013bc04f321026a057618e7
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cd3be9843247edb8fc6fcd8d8237cbce2bc19f5e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fa5bef5e80c6a3321b2b1a7070436f3bc5daf07c

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card