# CVE-2026-98156: drm/virtio: use the DMA API for resource backing on Xen

CVE-2026-98156 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-98156, released October 2, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-98156
- Priority: High
- CVSS: 7.8 (Moderate)
- EPSS: 0.0014
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Sep 25, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-98156

## Description

In the Linux kernel, the following vulnerability has been resolved:  drm/virtio: use the DMA API for resource backing on Xen  On a Xen PV domain page addresses bear no relation to the real machine addresses the host would have to use to reach it. virtio_ring.c handles this correctly, vring_use_map_api() returns true for any xen_domain() regardless of VIRTIO_F_ACCESS_PLATFORM.  virtio-gpu makes the same decision independently, but its copy looks only at the feature bit:  	bool use_dma_api = !virtio_has_dma_quirk(vgdev->vdev);  QEMU does not set iommu_platform on virtio-vga by default, so VIRTIO_F_ACCESS_PLATFORM is not negotiated, use_dma_api is false, and virtio_gpu_object_shmem_init() describes the framebuffer's backing pages to the host with sg_phys().  Those are guest-physical addresses. In a PV domain they resolve, on the host side, to pages belonging to some other domain, so the host scans out unrelated memory.  Move the decision into virtio_gpu_use_dma_api() and give it the xen_domain() check, like vring_use_map_api() has. This additionally enables the dma_sync_sgtable_for_device() calls in virtgpu_vq.c, which are required for correctness whenever swiotlb is in play.  Reproduced with a Xen 4.21 PV dom0 nested inside QEMU 8.2 with virtio-vga, on both a distro 6.8 kernel and 6.18 LTS. A PVH dom0 works fine and doesn't need this fix because it is identity-mapped, only PV dom0s are affected.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel-livepatch-6.18.54-121.166 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2026-98156](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98156.md) | Oct 2, 2026 |
| Linux | linux Debian 14 | 7.2.7-1 | [DEBIAN-CVE-2026-98156](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98156.md) | Oct 2, 2026 |
| Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.54-121.166.amzn2023 | [ALAS2023-2026-3192](https://patchblox.com/security/data/fix/linux/alas2023-2026-3192.md) | Nov 7, 2026 |

---

Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
