Menu

Star on GitHub · 3.2k

CVE-2025-68760

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 wit…

Published Jan 5, 2026EPSS 0.18%

Overview

CVE-2025-68760 is a known-severity vulnerability. It was published on January 5, 2026.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68760?

CVE-2025-68760 is a known-severity vulnerability. It was published on January 5, 2026.

How severe is CVE-2025-68760?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68760?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68760?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68760 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.