CVE-2025-68760: iommu/amd: Fix potential out-of-bounds read in iommu_mmio_show
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 0ec4aaf5f3f559716a6559f3d6d9616e9470bed6, a0c7005333f9a968abb058b1d77bbcd7fb7fd1e7, b959df804c33913dbfdb90750f2d693502b3d126.
Low priority for now. Upgrade to Linux Linux 0ec4aaf5f3f559716a6559f3d6d9616e9470bed6, a0c7005333f9a968abb058b1d77bbcd7fb7fd1e7, b959df804c33913dbfdb90750f2d693502b3d126 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 5, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.17affected
- 7a4ee419e8c144b747a8915856e91a034d7c8f34 and later · before b959df804c33913dbfdb90750f2d693502b3d126affected · git
- 7a4ee419e8c144b747a8915856e91a034d7c8f34 and later · before 0ec4aaf5f3f559716a6559f3d6d9616e9470bed6affected · git
- 7a4ee419e8c144b747a8915856e91a034d7c8f34 and later · before a0c7005333f9a968abb058b1d77bbcd7fb7fd1e7affected · git
- before 6.17not affected · semver
- 6.17.13 and later · up to and including 6.17.*not affected · semver
- 6.18.2 and later · up to and including 6.18.*not affected · semver
- 6.19 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68758Jan 5, 2026 · backlight: led-bl: Add devlink to supplier LEDs0Monitor
- ← EarlierCVE-2025-68759Jan 5, 2026 · wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring()0Monitor
- Later →CVE-2025-68761Jan 5, 2026 · hfs: fix potential use after free in hfs_correct_next_unused_CNID()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ec4aaf5f3f559716a6559f3d6d9616e9470bed6 | Vendor (CNA) |
| Linux Linux | a0c7005333f9a968abb058b1d77bbcd7fb7fd1e7 | Vendor (CNA) |
| Linux Linux | b959df804c33913dbfdb90750f2d693502b3d126 | Vendor (CNA) |
| debian:linux | 6.17.13-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.