CVE-2024-27050
Last modified
CVE-2024-27050 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.6.23 |
| Linux | Linux Kernel | >= 6.7, < 6.7.11 |
| Linux | Linux Kernel | >= 6.8, < 6.8.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-27050?
How severe is CVE-2024-27050?
How do I fix CVE-2024-27050?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-27045In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27046In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27047In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27048In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27049In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-2705A vulnerability, which was classified as critical, has been …8.8
- CVE-2024-27051In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27052In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27053In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2024-27054In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27055Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-27056In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-27050?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
