LiveActive security incident?Get immediate response
CVE Record

CVE-2024-44994: iommu: Restore lost return in iommu_report_device_fault()

In the Linux kernel, the following vulnerability has been resolved: iommu: Restore lost return in iommu_report_device_fault() When iommu_report_device_fault gets called with a partial fault it is supposed to collect the fault into the group and then return. Instead the return was accidently deleted which results in trying to process the fault and an eventual crash. Deleting the return was a typo, put it back.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A missing return statement in Linux IOMMU fault handling can make the kernel continue processing an incomplete device fault and eventually crash. This creates a serious stability and availability concern for affected systems. The supplied record scores it 8.8, although its description specifically demonstrates a crash rather than confirmed data theft or modification.

Executive priority

Treat this as a high-priority kernel availability issue, especially on shared compute, virtualization, and device-assignment hosts. Patch through normal vendor channels promptly. Emergency internet-edge action is not justified by the supplied evidence because the stated attack vector is local and active exploitation is unconfirmed.

Technical view

When iommu_report_device_fault() receives a partial fault, it should add the fault to its group and return. A deleted return allowed execution to continue with incomplete fault data, eventually crashing the kernel. The referenced Linux stable commits restore the return. Exposure depends on running an affected kernel and reaching this IOMMU partial-fault path.

Likely exposure

The bundle identifies Linux kernel versions including 6.9, 6.10.7, and 6.11 as affected, but its version-array semantics are incomplete. Prioritize systems using IOMMU-enabled devices, virtualization, device assignment, or related fault-reporting functionality. The CVSS vector requires local access with low privileges; remote-only exposure is not supported by the supplied evidence.

Exploitation context

The supplied CVSS vector indicates local, low-privileged attack conditions without user interaction. The source description confirms an eventual kernel crash. It does not establish practical confidentiality or integrity compromise, public exploit availability, or observed exploitation. The record is not marked as included in CISA KEV.

Researcher notes

The root cause is a control-flow regression: partial faults were grouped, but execution did not stop afterward. The two kernel.org references are the authoritative correction records supplied. Researchers should distinguish the demonstrated crash from the broader CVSS confidentiality and integrity ratings, which are not explained by the description. Exact downstream package boundaries require vendor confirmation.

Mitigation direction

  • Identify affected kernels and map distribution package versions against vendor advisories and the referenced stable commits.
  • Upgrade to a vendor-supported kernel containing the correction for the applicable kernel branch.
  • Prioritize IOMMU-enabled hosts supporting virtualization, device assignment, or untrusted local workloads.
  • If upgrading is delayed, consult the distribution vendor for supported mitigations; none are specified in the bundle.

Validation and detection

  • Record each system's running kernel and distribution package version.
  • Confirm the applicable vendor kernel includes one of the referenced fixes or an equivalent backport.
  • Review kernel logs and crash records for IOMMU device faults near unexplained outages.
  • After updating, verify the corrected kernel is running and repeat normal IOMMU-dependent workload testing.
Prepared
Confidence
high
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-44994 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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.

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

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H26Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-44994Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3dfa64aecbafc288216b2790438d395add192c30, 3dfa64aecbafc288216b2790438d395add192c30unaffected
LinuxLinux6.9, 0, 6.10.7, 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.