LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27079: iommu/vt-d: Fix NULL domain on device release

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix NULL domain on device release In the kdump kernel, the IOMMU operates in deferred_attach mode. In this mode, info->domain may not yet be assigned by the time the release_device function is called. It leads to the following crash in the crash kernel: BUG: kernel NULL pointer dereference, address: 000000000000003c ... RIP: 0010:do_raw_spin_lock+0xa/0xa0 ... _raw_spin_lock_irqsave+0x1b/0x30 intel_iommu_release_device+0x96/0x170 iommu_deinit_device+0x39/0xf0 __iommu_group_remove_device+0xa0/0xd0 iommu_bus_notifier+0x55/0xb0 notifier_call_chain+0x5a/0xd0 blocking_notifier_call_chain+0x41/0x60 bus_notify+0x34/0x50 device_del+0x269/0x3d0 pci_remove_bus_device+0x77/0x100 p2sb_bar+0xae/0x1d0 ... i801_probe+0x423/0x740 Use the release_domain mechanism to fix it. The scalable mode context entry which is not part of release domain should be cleared in release_device().

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can crash a kdump crash kernel on systems using Intel VT-d IOMMU when a device is released before its domain is assigned. The main business concern is reliability during crash recovery and forensic capture, not proven remote compromise.

Executive priority

Treat as a reliability and recovery-risk issue. Patch through normal kernel maintenance, with higher urgency for production systems where crash dumps support incident response, outage analysis, or regulatory evidence preservation.

Technical view

The Intel IOMMU release path can dereference a NULL info->domain in deferred_attach mode used by kdump kernels. The upstream fix uses the release_domain mechanism and clears scalable-mode context entries in release_device when they are outside the release domain.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with Intel VT-d IOMMU and kdump crash-kernel workflows. The source lists Linux kernel ranges including 5.18 through fixed 6.8.2 and 6.9 context, but distribution backports require vendor verification.

Exploitation context

The supplied sources do not show active exploitation, public exploit availability, or KEV listing. The described outcome is a NULL pointer dereference crash in the crash kernel during device release, triggered in a specific kdump deferred_attach path.

Researcher notes

Evidence is strongest for root cause and fix direction from Linux stable references. The bundle lacks CVSS, CWE, detailed affected distribution mapping, and exploitability analysis, so avoid claiming broader impact beyond the documented kdump crash-kernel NULL dereference.

Mitigation direction

  • Update to a Linux kernel or vendor build containing the referenced stable fixes.
  • Check distribution advisories for backported fixes matching CVE-2024-27079.
  • Prioritize systems relying on kdump for incident recovery or root-cause analysis.
  • Review Intel VT-d IOMMU and kdump usage across affected Linux fleets.

Validation and detection

  • Inventory Linux kernel versions and vendor patch levels on systems using kdump.
  • Confirm whether Intel VT-d IOMMU is enabled on potentially affected hosts.
  • Verify vendor kernel changelogs reference CVE-2024-27079 or the stable commits.
  • Test kdump behavior after patching in a controlled maintenance window.
Prepared
Confidence
medium
Sources
4

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-2024-27079 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
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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux586081d3f6b13ec9dfdfdf3d7842a688b376fa5e, 586081d3f6b13ec9dfdfdf3d7842a688b376fa5eunaffected
LinuxLinux5.18, 0, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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