CVE-2026-31735
published 2026-05-01CVE-2026-31735: In the Linux kernel, the following vulnerability has been resolved: iommupt: Fix short gather if the unmap goes into a large mapping unmap has the odd behavior…
PriorityP341high8.8CVSS 3.1
AVLACLPRLUINSCCHIHAH
EPSS
0.12%
2.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
iommupt: Fix short gather if the unmap goes into a large mapping
unmap has the odd behavior that it can unmap more than requested if the
ending point lands within the middle of a large or contiguous IOPTE.
In this case the gather should flush everything unmapped which can be
larger than what was requested to be unmapped. The gather was only
flushing the range requested to be unmapped, not extending to the extra
range, resulting in a short invalidation if the caller hits this special
condition.
This was found by the new invalidation/gather test I am adding in
preparation for ARMv8. Claude deduced the root cause.
As far as I remember nothing relies on unmapping a large entry, so this is
likely not a triggerable bug.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 7c53f4238aa8bfb476e177263133ead2eeb8d55d < 50ecd96a28f712f8b682c0441f4cb9b086d28816 | 50ecd96a28f712f8b682c0441f4cb9b086d28816 |
| linux | linux | >= 7c53f4238aa8bfb476e177263133ead2eeb8d55d < ee6e69d032550687a3422504bfca3f834c7b5061 | ee6e69d032550687a3422504bfca3f834c7b5061 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 6.19 < 6.19.12 | 6.19.12 |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: iommupt: Fix short gather if the unmap goes into a large mapping
vendor_redhat·2026-05-01·CVSS 5.5
CVE-2026-31735 [MEDIUM] CWE-459 kernel: iommupt: Fix short gather if the unmap goes into a large mapping
kernel: iommupt: Fix short gather if the unmap goes into a large mapping
A flaw was found in the Linux kernel's Input/Output Memory Management Unit (IOMMU) page table handling. When an unmap operation partially overlaps with a large memory mapping, the system's invalidation process may not correctly flush the entire unmapped range. This could result in a 'short invalidation,' where some memory remains improperly invalidated. While this issue could potentially lead to data integrity problems or information disclosure, it is currently considered unlikely to be a triggerable bug.
Package: kernel (Red Hat Enterprise Linux 10) - Fix deferred
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat En
GHSA
GHSA-3h92-2gxm-w9x7: In the Linux kernel, the following vulnerability has been resolved:
iommupt: Fix short gather if the unmap goes into a large mapping
unmap has the o
ghsa_unreviewed·2026-05-01
CVE-2026-31735 [HIGH] GHSA-3h92-2gxm-w9x7: In the Linux kernel, the following vulnerability has been resolved:
iommupt: Fix short gather if the unmap goes into a large mapping
unmap has the o
In the Linux kernel, the following vulnerability has been resolved:
iommupt: Fix short gather if the unmap goes into a large mapping
unmap has the odd behavior that it can unmap more than requested if the
ending point lands within the middle of a large or contiguous IOPTE.
In this case the gather should flush everything unmapped which can be
larger than what was requested to be unmapped. The gather was only
flushing the range requested to be unmapped, not extending to the extra
range, resulting in a short invalidation if the caller hits this special
condition.
This was found by the new invalidation/gather test I am adding in
preparation for ARMv8. Claude deduced the root cause.
As far as I remember nothing relies on unmapping a large entry, so this is
likely not a triggerable bug.
No detection rules found.
No public exploits indexed.
2026-05-01
Published