Public vulnerability disclosure

CVE-2026-99685

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

published

In the Linux kernel, the following vulnerability has been resolved: iommu/virtio: Reset device before deleting virtqueues on probe failure viommu_probe() marks the device DRIVER_OK before populating the event virtqueue and registering the IOMMU device in sysfs. viommu_fill_evtq() hands the device a set of device-writable buffers through virtqueue_add_inbuf(), 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 devm_kmalloc_array() 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 viommu_remove() already does.

Technical severity8.4 highCVSS 3.1 · CNA: Linux
Published2026-11-20Source updated 2026-11-22
Collected2026-11-223 attributed sources

Fixes and workarounds

No remediation reported in collected sources.

Missing remediation information is not evidence that no patch exists.

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Linux
Linux
≥ edcd69ab9a323b7ac7a86e1c44b6c9c46598391f; < e09d65fd554b78c7277f6379517c773ff36d55d1 (affected, git)
≥ edcd69ab9a323b7ac7a86e1c44b6c9c46598391f; < e60e6db9d07b2ebaff2e055a086fa8e8d14f565c (affected, git)
≥ edcd69ab9a323b7ac7a86e1c44b6c9c46598391f; < cfdb3b6915299ebb6ffc98566f9cf73d4d1f1598 (affected, git)
≥ edcd69ab9a323b7ac7a86e1c44b6c9c46598391f; < 1f8efac19a0870cdfdf8477e447e5a07ddce9623 (affected, git)
Other versions: unaffected
CNA: Linux
Linux
Linux
5.3 (affected)
≥ 0; < 5.3 (unaffected, semver)
≥ 6.12.118; ≤ 6.12.* (unaffected, semver)
≥ 6.18.64; ≤ 6.18.* (unaffected, semver)
≥ 7.3.5; ≤ 7.3.* (unaffected, semver)
≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix)
Other versions: affected
CNA: Linux

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 8.4
high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCNA: Linux
3.1 / 8.4
high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HNVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide