LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48867: dmaengine: idxd: Prevent use after free on completion memory

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Prevent use after free on completion memory On driver unload any pending descriptors are flushed at the time the interrupt is freed: idxd_dmaengine_drv_remove() -> drv_disable_wq() -> idxd_wq_free_irq() -> idxd_flush_pending_descs(). If there are any descriptors present that need to be flushed this flow triggers a "not present" page fault as below: BUG: unable to handle page fault for address: ff391c97c70c9040 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page The address that triggers the fault is the address of the descriptor that was freed moments earlier via: drv_disable_wq()->idxd_wq_free_resources() Fix the use after free by freeing the descriptors after any possible usage. This is done after idxd_wq_reset() to ensure that the memory remains accessible during possible completion writes by the device.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash kernel code when the idxd dmaengine driver unloads while pending descriptors still exist. The bug is a use-after-free in completion memory handling. The public record does not provide CVSS scoring or evidence of active exploitation, so urgency depends on whether affected Linux kernels and the idxd driver are present.

Executive priority

Treat this as a targeted Linux kernel maintenance item, not an emergency based on current evidence. Prioritize affected infrastructure that uses the idxd driver or related accelerator hardware, and roll the fix into normal kernel update cycles unless local crash evidence raises urgency.

Technical view

During idxd driver removal, pending descriptors may be flushed after descriptor memory was freed, causing a kernel page fault from use-after-free. The resolved fix keeps descriptor memory accessible until after reset and possible device completion writes. Source version data is limited and should be verified against kernel stable commits.

Likely exposure

Likely limited to Linux systems running affected kernel builds with the idxd dmaengine driver enabled or in use. Systems without this driver loaded, or already carrying the referenced stable fixes, are less likely exposed. The provided version data is not detailed enough for precise range mapping.

Exploitation context

The sources describe a fault during driver unload with pending descriptors. CISA KEV is false in the bundle, and no cited source states active exploitation. The available evidence supports a reliability or denial-of-service concern, not confirmed remote exploitation or privilege escalation.

Researcher notes

The root issue is ordering during idxd teardown: descriptors can be freed before all possible completion usage ends. The public bundle lacks CVSS, CWE, and precise affected range detail. Validate exposure by driver usage and patch provenance rather than assuming all Linux hosts are affected.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-48867 and idxd fixes.
  • Update to a kernel build containing the referenced stable commits.
  • Prioritize systems that use idxd, DMA engine features, or Intel accelerator hardware.
  • If patching is delayed, review whether idxd can be disabled safely.
  • Monitor kernel logs for idxd unload faults or related page faults.

Validation and detection

  • Inventory Linux kernel versions across exposed fleets.
  • Check whether the idxd driver is built, loaded, or used.
  • Compare kernel source or package changelog against the referenced commits.
  • Review crash logs for page faults during idxd driver unload.
  • Confirm remediation through vendor package metadata, not version guesses.
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-2022-48867 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
LinuxLinux63c14ae6c161dec8ff3be49277edc75a769e054a, 63c14ae6c161dec8ff3be49277edc75a769e054aunaffected
LinuxLinux5.19, 0, 6.1.8, 6.2affected
Weakness

CWE details

No CWE listed

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