CVE-2026-99685: iommu/virtio: Reset device before deleting virtqueues on probe failure

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

iommu/virtio: Reset device before deleting virtqueues on probe failure

viommuprobe() marks the device DRIVEROK before populating the event virtqueue and registering the IOMMU device in sysfs. viommufillevtq() hands the device a set of device-writable buffers through virtqueueaddinbuf(), so from that point on the device may write into them and into the rings.

If either step fails, the error path deletes the virtqueues without resetting the device first. The event buffers are allocated with devmkmallocarray() and are released as probe unwinds, so the device can go on writing to memory that has been freed.

Reset the device before deleting the virtqueues, the way viommuremove() already does.

Affected Software

3 affected componentsFixes available
linux/kernel>=5.3.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Compensating control

    On probe failure, reset the device before deleting the virtqueues so it cannot continue writing to freed event-buffer memory.

Frequently Asked Questions

1

Under what conditions can this occur?

The issue is reachable when virtio-IOMMU probing has already marked the device DRIVER_OK and supplied event-queue buffers, but then fails while populating the event virtqueue or registering the IOMMU device in sysfs.

2

What is the security impact of the failed probe path?

Without a device reset, the device may continue writing to event buffers and virtqueue rings after the error path deletes the virtqueues and probe cleanup frees the event-buffer memory. This results in device writes to freed memory.

3

What mitigation is available if an update cannot be applied immediately?

The provided data does not identify a configuration workaround. The corrective change resets the virtio-IOMMU device before deleting virtqueues when probing fails.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203