CVE-2024-44932
Last modified
CVE-2024-44932 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: idpf: fix UAFs when destroying the queues The second tagged commit started sometimes (very rarely, but possible) throwing WARNs from net/core/page_pool.c:page_pool_disable_direct_recycling(). Turned out idpf frees interrupt vectors with embedded NAPIs *before* freeing the queues making page_pools' NAPI pointers lead to freed memory before these pools are destroyed by libeth. It's not clear whether there are other accesses to the freed vectors when destroying the queues, but anyway, we usually free queue/interrupt vectors only when the queues are destroyed and the NAPIs are guaranteed to not be referenced anywhere. Invert the allocation and freeing logic making queue/interrupt vectors be allocated first and freed last. Vectors don't require queues to be present, so this is safe. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: idpf: fix UAFs when destroying the queues The second tagged commit started sometimes (very rarely, but possible) throwing WARNs from net/core/page_pool.c:page_pool_disable_direct_recycling(). Turned out idpf frees interrupt vectors with embedded NAPIs *before* freeing the queues making page_pools' NAPI pointers lead to freed memory before these pools are destroyed by libeth. It's not clear whether there are other accesses to the freed vectors when destroying the queues, but anyway, we usually free queue/interrupt vectors only when the queues are destroyed and the NAPIs are guaranteed to not be referenced anywhere. Invert the allocation and freeing logic making queue/interrupt vectors be allocated first and freed last. Vectors don't require queues to be present, so this is safe. Additionally, this change allows to remove that useless queue->q_vector pointer cleanup, as vectors are still valid when freeing the queues (+ both are freed within one function, so it's not clear why nullify the pointers at all).
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 | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.10.5 | — |
| Linux | Linux Kernel | 6.11 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-44932?
How severe is CVE-2024-44932?
How do I fix CVE-2024-44932?
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-4492A vulnerability, which was classified as critical, has been …8.8
- CVE-2024-44920A cross-site scripting (XSS) vulnerability in the component …6.1
- CVE-2024-44921SeaCMS v12.9 was discovered to contain a SQL injection vulne…9.8
- CVE-2024-4493A vulnerability, which was classified as critical, was found…8.8
- CVE-2024-44930Serilog before v2.1.0 was discovered to contain a Client IP …6.5
- CVE-2024-44931In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-44933In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-44934In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-44935In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-44936In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-44937In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-44938In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-44932?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
