LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53789: iommu/amd: Improve page fault error reporting

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Improve page fault error reporting If IOMMU domain for device group is not setup properly then we may hit IOMMU page fault. Current page fault handler assumes that domain is always setup and it will hit NULL pointer derefence (see below sample log). Lets check whether domain is setup or not and log appropriate message. Sample log: ---------- amdgpu 0000:00:01.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6 BUG: kernel NULL pointer dereference, address: 0000000000000058 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 2 PID: 56 Comm: irq/24-AMD-Vi Not tainted 6.2.0-rc2+ #89 Hardware name: xxx RIP: 0010:report_iommu_fault+0x11/0x90 [...] Call Trace: <TASK> amd_iommu_int_thread+0x60c/0x760 ? __pfx_irq_thread_fn+0x10/0x10 irq_thread_fn+0x1f/0x60 irq_thread+0xea/0x1a0 ? preempt_count_add+0x6a/0xa0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xe9/0x110 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK> [joro: Edit commit message]

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash the kernel’s AMD IOMMU fault handler when an IOMMU domain is missing. The public record describes a NULL pointer dereference during page-fault reporting. Business impact appears most likely to be availability disruption on affected AMD IOMMU systems, but severity and exploitability are not rated in the supplied sources.

Executive priority

Handle through normal kernel patch management unless critical AMD IOMMU systems are experiencing crashes. Raise priority for virtualization hosts, GPU workloads, or systems where unexpected reboot or kernel crash has business impact.

Technical view

The AMD IOMMU page fault handler assumed a device group always had a configured domain. If that assumption failed, report_iommu_fault could dereference NULL during AMD-Vi interrupt handling. The fix adds a domain presence check and logs an appropriate message instead of crashing.

Likely exposure

Exposure is most relevant to Linux systems using AMD IOMMU/AMD-Vi, potentially with GPU or device passthrough-style configurations. The source lists Linux kernel versions and stable commits, but distro-specific package status needs vendor mapping.

Exploitation context

The supplied sources do not show active exploitation, public exploit availability, or KEV listing. The record includes a crash log, not a weaponized attack path. Treat exploitation likelihood as unclear from the available evidence.

Researcher notes

Evidence supports a kernel NULL pointer dereference in AMD IOMMU fault reporting. The CVE record lacks CVSS, CWE, exploit status, and clear attack prerequisites. Avoid over-scoping beyond Linux AMD IOMMU paths and validate fixed versions through downstream kernel vendors.

Mitigation direction

  • Update to a Linux kernel containing the referenced AMD IOMMU fix.
  • Use distribution advisories to map the fix to package versions.
  • Prioritize AMD IOMMU/AMD-Vi hosts and virtualization or passthrough systems.
  • Monitor kernel logs for AMD-Vi page fault crashes until patched.

Validation and detection

  • Inventory Linux kernel versions on AMD IOMMU-capable systems.
  • Confirm whether vendor kernel packages include the referenced stable commits.
  • Review logs for report_iommu_fault or amd_iommu_int_thread crashes.
  • Check whether IOMMU is enabled on exposed or critical hosts.
Prepared
Confidence
medium
Sources
5

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-2023-53789 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
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9f78e446bde812d18f228976f2c6b8f25b93f08b, 9f78e446bde812d18f228976f2c6b8f25b93f08b, 9f78e446bde812d18f228976f2c6b8f25b93f08bunaffected
LinuxLinux5.16, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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