Skip to content

SystemsHigh 8.4Patch available

CVE-2026-99685

Linux kernel iommu/virtio probe bug allows device writes to freed memory (use-after-free).

How scary is it?

updated 22 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • No

    Reachable over the network1

    Needs local access to the machine, such as a shell or a logged-in user (CVSS AV:L).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Linux in an affected version>= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e09d65fd554b78c7277f6379517c773ff36d55d1 / >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e60e6db9d07b2ebaff2e055a086fa8e8d14f565c / >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < cfdb3b6915299ebb6ffc98566f9cf73d4d1f1598 (+2 more)

    >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e09d65fd554b78c7277f6379517c773ff36d55d1 >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e60e6db9d07b2ebaff2e055a086fa8e8d14f565c >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < cfdb3b6915299ebb6ffc98566f9cf73d4d1f1598 >= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < 1f8efac19a0870cdfdf8477e447e5a07ddce9623 5.3

    Vendor says fixed in: < 5.3, >= 6.12.118 and <= 6.12.*, >= 6.18.64 and <= 6.18.*, >= 7.3.5 and <= 7.3.*, >= 7.4-rc2 and <= *.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker already has local access to the machine

    CVSS attack vector: Local (AV:L). Local access required, such as a shell or a logged-in user.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release< 5.3 / >= 6.12.118 and <= 6.12.* / >= 6.18.64 and <= 6.18.* / >= 7.3.5 and <= 7.3.* (+1 more)

    Linux: < 5.3, >= 6.12.118 and <= 6.12.*, >= 6.18.64 and <= 6.18.*, >= 7.3.5 and <= 7.3.*, >= 7.4-rc2 and <= *

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenApply kernel updates with the provided patch and reboot affected systems.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

CVSS
8.4Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
No score yet
Fix
Fixed in < 5.3, >= 6.12.118 and <= 6.12.*, >= 6.18.64 and <= 6.18.*per the vendor; 2 more listed below
Published
20 Nov 2026analysed here 22 Nov 2026

Do first. Upgrade to a fixed release: < 5.3, >= 6.12.118 and <= 6.12.*, >= 6.18.64 and <= 6.18.*, >= 7.3.5 and <= 7.3.* (and 1 more below).

Summary

Impact

Device or guest-controlled virtio can write freed kernel memory, causing corruption that may lead to privilege escalation or kernel code execution.

Triage

Exploitable
At runtime
Attack vector
local
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Linux>= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e09d65fd554b78c7277f6379517c773ff36d55d1>= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < e60e6db9d07b2ebaff2e055a086fa8e8d14f565c>= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < cfdb3b6915299ebb6ffc98566f9cf73d4d1f1598>= edcd69ab9a323b7ac7a86e1c44b6c9c46598391f and < 1f8efac19a0870cdfdf8477e447e5a07ddce96235.3Vendor says fixed in: < 5.3, >= 6.12.118 and <= 6.12.*, >= 6.18.64 and <= 6.18.*, >= 7.3.5 and <= 7.3.*, >= 7.4-rc2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Linux kernel (iommu/virtio drivers)
  • Virtual machines using virtio devices
  • Hosts with IOMMU-backed virtio hardware

Fix and mitigation

Action required

Patch when possible

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 20 Nov 2026Published
  2. 22 Nov 2026CVE record last updated2 days later
  3. 22 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-99685 being exploited?

Not confirmed. CVE-2026-99685 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-99685?

CVE-2026-99685 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-99685?

Yes. A fix has been recorded for CVE-2026-99685. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-99685 affect?

CVE-2026-99685 affects Linux kernel (iommu/virtio drivers), Virtual machines using virtio devices, Hosts with IOMMU-backed virtio hardware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-99685?

Apply kernel updates with the provided patch and reboot affected systems.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Other links (4)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.