LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68760: iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show In iommu_mmio_write(), it validates the user-provided offset with the check: `iommu->dbg_mmio_offset > iommu->mmio_phys_end - 4`. This assumes a 4-byte access. However, the corresponding show handler, iommu_mmio_show(), uses readq() to perform an 8-byte (64-bit) read. If a user provides an offset equal to `mmio_phys_end - 4`, the check passes, and will lead to a 4-byte out-of-bounds read. Fix this by adjusting the boundary check to use sizeof(u64), which corresponds to the size of the readq() operation.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-68760 is a Linux kernel AMD IOMMU bounds-checking bug. A crafted offset can cause the kernel to read four bytes past the intended MMIO range. The sources do not provide CVSS, impact beyond out-of-bounds read, or evidence of exploitation.

Executive priority

Treat as a kernel maintenance item unless your environment exposes this path broadly. Patch through normal kernel update channels, with higher priority for AMD virtualization or infrastructure hosts.

Technical view

In iommu_mmio_write(), the offset check assumes a 4-byte access, while iommu_mmio_show() performs an 8-byte readq(). An offset at mmio_phys_end - 4 passes validation and allows a 4-byte out-of-bounds read. Kernel stable commits adjust the boundary check to sizeof(u64).

Likely exposure

Exposure appears limited to affected Linux kernels using the AMD IOMMU code path and the interface accepting this MMIO offset. The bundle does not establish remote reachability, privilege requirements, or affected distributions.

Exploitation context

No cited source or KEV entry indicates active exploitation. The provided evidence describes a boundary-check flaw and its kernel fix, but not real-world abuse, public exploit code, or full impact.

Researcher notes

The key issue is a size mismatch between validation and access width: a 4-byte boundary check protects an 8-byte read. Evidence is limited to the CVE text and Linux stable commit references.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixed kernel packages.
  • Restrict access to interfaces that expose AMD IOMMU MMIO offset controls.
  • Prioritize systems with AMD IOMMU enabled until vendor impact guidance is clear.

Validation and detection

  • Inventory Linux kernel versions across AMD-based systems.
  • Confirm whether deployed kernels include the referenced stable commits or distro backports.
  • Review host configuration for AMD IOMMU use and exposed diagnostic interfaces.
  • Track CVE and vendor advisories for severity, CVSS, and distribution-specific fixes.
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-2025-68760 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
LinuxLinux7a4ee419e8c144b747a8915856e91a034d7c8f34, 7a4ee419e8c144b747a8915856e91a034d7c8f34, 7a4ee419e8c144b747a8915856e91a034d7c8f34unaffected
LinuxLinux6.17, 0, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

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