# CVE-2024-44932: idpf: fix UAFs when destroying the queues

> A use-after-free vulnerability in the Linux kernel idpf driver allows attackers to potentially execute code or escalate privileges by exploiting improper memory deallocation order during queue destruction.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2024-44932, DEBIAN-CVE-2024-44932, GHSA-h3w8-q2j6-4h9m, ROOT-OS-UBUNTU-2404-CVE-2024-44932, UBUNTU-CVE-2024-44932

## What is CVE-2024-44932?

CVE-2024-44932 is a high-severity use after free vulnerability in Linux kernel, published on 26 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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).

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-44932?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-44932?

Apply the vendor's patch.

## Is CVE-2024-44932 being exploited?

There is no known exploitation of CVE-2024-44932 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44932 and fix it if it is affected.

What it is: CVE-2024-44932 is a high-severity use after free vulnerability in Linux kernel, published on 26 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-44932 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-44932/ (Markdown: https://insights.sbomify.com/CVE-2024-44932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-44932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-44932
- OSV: https://osv.dev/vulnerability/CVE-2024-44932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-44932/
Summaries are generated and may contain mistakes; the official description above is the record.