LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-44932 is a Linux kernel memory safety bug in the idpf network driver. During queue teardown, interrupt vectors containing NAPI state could be freed before related queues, leaving stale pointers. The public data does not show active exploitation, CVSS, or a vendor workaround beyond the kernel fix references.

Executive priority

Treat this as a targeted kernel maintenance item, not an internet-wide emergency based on available evidence. Prioritize systems using the idpf driver because kernel use-after-free bugs can affect reliability and may carry security risk even when exploitability is not proven.

Technical view

The issue is a use-after-free during idpf queue destruction. Page-pool NAPI pointers could reference freed interrupt-vector memory because vectors were released before queues. The fix inverts allocation/free ordering so queue/interrupt vectors are allocated first and freed last, keeping NAPI references valid during teardown.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with the idpf driver in use. The source bundle names Linux 6.7, 6.10.5, and 6.11-related version data, but distribution backport status must be verified with the OS vendor.

Exploitation context

The source describes rare WARNs during queue destruction and identifies use-after-free conditions. It does not provide evidence of exploitation, public exploit availability, KEV listing, privilege requirements, or remotely reachable attack conditions.

Researcher notes

Evidence is limited to the kernel CVE description and stable commit references. The key condition is teardown ordering between idpf queues, interrupt vectors, NAPI pointers, and page_pool cleanup. No CVSS, CWE, exploit status, or complete affected distribution matrix is provided.

Mitigation direction

  • Check OS vendor advisories for CVE-2024-44932 and idpf driver fixes.
  • Upgrade to a vendor kernel containing the referenced stable fixes.
  • Prioritize hosts using idpf-supported network hardware or virtual functions.
  • If patching is delayed, review vendor guidance for driver-specific mitigations.

Validation and detection

  • Inventory running kernel versions and whether the idpf module is loaded.
  • Confirm vendor kernel changelog includes CVE-2024-44932 or the referenced stable commits.
  • Review kernel logs for idpf, NAPI, page_pool, or queue teardown warnings.
  • Validate patched systems after reboot into the updated kernel.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-44932 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1c325aac10a82f11410da8a2bf35e3e410a42751, 1c325aac10a82f11410da8a2bf35e3e410a42751unaffected
LinuxLinux6.7, 0, 6.10.5, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.