LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48724: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() After commit e3beca48a45b ("irqdomain/treewide: Keep firmware node unconditionally allocated"). For tear down scenario, fn is only freed after fail to allocate ir_domain, though it also should be freed in case dmar_enable_qi returns error. Besides free fn, irq_domain and ir_msi_domain need to be removed as well if intel_setup_irq_remapping fails to enable queued invalidation. Improve the rewinding path by add out_free_ir_domain and out_free_fwnode lables per Baolu's suggestion.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-48724 is a Linux kernel memory leak in Intel VT-d interrupt-remapping setup error handling. The available sources describe cleanup that was incomplete after a failed queued-invalidation enablement path. Business risk is unclear because no CVSS, CWE, or exploitation evidence is provided.

Executive priority

Handle through normal kernel patch management unless local evidence shows affected high-value systems or vendor guidance raises severity. There is no provided evidence of exploitation or a defined CVSS score.

Technical view

In intel_setup_irq_remapping(), if dmar_enable_qi returned an error, the teardown path failed to free the firmware node and remove related IRQ domains. Kernel stable fixes add cleanup labels to free fn and remove irq_domain and ir_msi_domain on that failure path.

Likely exposure

Exposure is limited to Linux systems using affected kernel versions and Intel VT-d interrupt remapping code paths. The source bundle lists Linux kernel versions and commits, but affectedness should be validated against the exact running kernel and distribution backport status.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. The described issue is a memory leak on an initialization failure path, not a disclosed remote code execution or privilege escalation path in the provided evidence.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. The core issue is cleanup correctness after dmar_enable_qi failure. Avoid assuming exploitability beyond memory leakage without additional vendor or kernel maintainer analysis.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check distribution security advisories for backported fixes.
  • Prioritize internet-facing or high-availability Linux hosts if affected.
  • Monitor vendor guidance for severity or mitigation updates.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Compare running kernels with distribution fixed-version advisories.
  • Confirm whether hosts use Intel VT-d interrupt remapping.
  • Review kernel change logs for the referenced fix commits.
Prepared
Confidence
medium
Sources
9

Public sources used

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-48724 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
2ADP providers
8Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux03992c88d71ba79d956f2ed54e370e630b8750f4, c0c489e5430530a7021f4c889cd5931597e4b200, 36f7355545725c5e9400520ae33e6ee16cf78c0e, e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, b4198ecddb87cd955aa9e024dd656af5ceaf6196, 4.14.190, 4.19.135, 5.4.54, 5.7.11unaffected
LinuxLinux5.8, 0, 4.14.265, 4.19.228, 5.4.178, 5.10.99, 5.15.22, 5.16.8, 5.17affected
Weakness

CWE details

No CWE listed

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