Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90243

iommu/vt-d: Clear Present bit before tearing down copied context entry

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Clear Present bit before tearing down copied context entry copied_context_tear_down() zeroes the 128-bit context entry with context_clear_entry() while the Present bit is still set, and only then issues the context-cache and IOTLB invalidations. This leaves a window in which hardware can fetch a torn entry, with some fields already zeroed while Present is still set, leading to unpredictable behaviour or spurious faults. While x86 provides strong write ordering, the compiler may reorder the writes to the two 64-bit halves of the entry, and the hardware fetch is not guaranteed to be atomic with respect to multiple CPU writes. There is no cacheline flush before the invalidation either, so on an IOMMU without coherent access to the context table the zeroed entry may not be visible to hardware at the point the invalidation is submitted. Apply the same ownership handshake described in the VT-d spec, Section 6.5.3.3 ("Guidance to Software for Invalidations"): clear only the Present bit, flush it out to the IOMMU, perform the invalidations, and only then zero the remainder of the entry.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90243, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.1CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.1CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.1.

Affected products

  • Linux · Linux

    • affected c7191984e5aade540f1a3845a116537c89572655 – < 97750a8dce79c1a9b2b2d2a020b61b800141996c
    • affected c7191984e5aade540f1a3845a116537c89572655 – < 3c88cfedc7768b1ae2dc7ddc71547ae9a1aaff7d
    • affected c7191984e5aade540f1a3845a116537c89572655 – < 6b822d18c33af9d1e16a8e5e6aa6e656987b09de
    • affected c7191984e5aade540f1a3845a116537c89572655 – < f532c57985b1a7d6b7e37e05506b46d413e5cca4
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90243 badge
[![CVE-2026-90243](https://cveledger.app/badge/CVE-2026-90243.svg)](https://cveledger.app/cve/CVE-2026-90243)

Record last updated .