LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48894: iommu/arm-smmu-v3: Don't unregister on shutdown

In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3: Don't unregister on shutdown Similar to SMMUv2, this driver calls iommu_device_unregister() from the shutdown path, which removes the IOMMU groups with no coordination whatsoever with their users - shutdown methods are optional in device drivers. This can lead to NULL pointer dereferences in those drivers' DMA API calls, or worse. Instead of calling the full arm_smmu_device_remove() from arm_smmu_device_shutdown(), let's pick only the relevant function call - arm_smmu_device_disable() - more or less the reverse of arm_smmu_device_reset() - and call just that from the shutdown path.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel shutdown flaw in the ARM SMMUv3 IOMMU driver. During shutdown, the driver could unregister IOMMU state while other device drivers still rely on it, causing kernel crashes or potentially worse behavior. It is most relevant to Linux systems running affected kernels on ARM SMMUv3-capable hardware.

Executive priority

Treat this as a targeted kernel maintenance issue for ARM Linux fleets, not a broad emergency. Prioritize patch validation where affected hardware is used in production, especially systems where controlled shutdown and reboot reliability matters.

Technical view

The arm-smmu-v3 shutdown path called iommu_device_unregister(), removing IOMMU groups without coordination with DMA API users. Because driver shutdown callbacks are optional, dependent drivers may still issue DMA API calls and hit NULL pointer dereferences or worse. The resolved behavior disables the SMMU device during shutdown instead of fully unregistering it.

Likely exposure

Exposure is likely limited to Linux systems using the arm-smmu-v3 driver on ARM SMMUv3 hardware and affected kernel builds. The bundle identifies Linux 6.1-related versions and references stable kernel fixes, but does not provide full distribution-specific package ranges.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. The described impact occurs around shutdown behavior and driver coordination, so available evidence supports a reliability and kernel-safety concern rather than an internet-exposed attack path.

Researcher notes

The source evidence is limited to the CVE record description and two Linux stable commit references. No CVSS, CWE, exploit evidence, or distribution-specific fixed versions are provided. Avoid extrapolating beyond ARM SMMUv3 shutdown behavior unless vendor advisories add details.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-48894 coverage.
  • Upgrade to a kernel build containing the referenced stable fixes.
  • Prioritize ARM SMMUv3 systems that require reliable shutdown or reboot behavior.
  • Track distribution backports, because package versions may differ from upstream kernel versions.

Validation and detection

  • Inventory Linux hosts using ARM SMMUv3-capable hardware.
  • Confirm whether running kernels include the stable fix commits.
  • Review crash logs for shutdown-time DMA API or IOMMU NULL pointer failures.
  • Check distribution security notes for exact fixed package versions.
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-2022-48894 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux57365a04c92126525a58bf7a1599ddfa832415e9, 57365a04c92126525a58bf7a1599ddfa832415e9unaffected
LinuxLinux6.1, 0, 6.1.7, 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.