---
id: CVE-2026-90243
title: |-
  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…
summary: |-
  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…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= c7191984e5aade540f1a3845a116537c89572655 <
    97750a8dce79c1a9b2b2d2a020b61b800141996c
  - >-
    Linux >= c7191984e5aade540f1a3845a116537c89572655 <
    3c88cfedc7768b1ae2dc7ddc71547ae9a1aaff7d
  - >-
    Linux >= c7191984e5aade540f1a3845a116537c89572655 <
    6b822d18c33af9d1e16a8e5e6aa6e656987b09de
  - >-
    Linux >= c7191984e5aade540f1a3845a116537c89572655 <
    f532c57985b1a7d6b7e37e05506b46d413e5cca4
  - Linux 6.12
published: '2026-09-17'
updated: '2026-09-18'
sourceUpdated: '2026-09-18T18:17:50.560'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-90243'
references:
  - url: 'https://git.kernel.org/stable/c/3c88cfedc7768b1ae2dc7ddc71547ae9a1aaff7d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6b822d18c33af9d1e16a8e5e6aa6e656987b09de'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/97750a8dce79c1a9b2b2d2a020b61b800141996c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f532c57985b1a7d6b7e37e05506b46d413e5cca4'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.00161
epssPercentile: 0.05754
ingestedAt: '2026-09-17T16:21:47.846Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.