CVE-2026-45894 (GCVE-0-2026-45894)
Vulnerability from cvelistv5 – Published: 2026-05-27 12:17 – Updated: 2026-08-05 12:28
VLAI
EPSS
VEX
Title
iommu/vt-d: Clear Present bit before tearing down PASID entry
Summary
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Clear Present bit before tearing down PASID entry
The Intel VT-d Scalable Mode PASID table entry consists of 512 bits (64
bytes). When tearing down an entry, the current implementation zeros the
entire 64-byte structure immediately using multiple 64-bit writes.
Since the IOMMU hardware may fetch these 64 bytes using multiple
internal transactions (e.g., four 128-bit bursts), updating or zeroing
the entire entry while it is active (P=1) risks a "torn" read. If a
hardware fetch occurs simultaneously with the CPU zeroing the entry, the
hardware could observe an inconsistent state, leading to unpredictable
behavior or spurious faults.
Follow the "Guidance to Software for Invalidations" in the VT-d spec
(Section 6.5.3.3) by implementing the recommended ownership handshake:
1. Clear only the 'Present' (P) bit of the PASID entry.
2. Use a dma_wmb() to ensure the cleared bit is visible to hardware
before proceeding.
3. Execute the required invalidation sequence (PASID cache, IOTLB, and
Device-TLB flush) to ensure the hardware has released all cached
references.
4. Only after the flushes are complete, zero out the remaining fields
of the PASID entry.
Also, add a dma_wmb() in pasid_set_present() to ensure that all other
fields of the PASID entry are visible to the hardware before the Present
bit is set.
Severity
7.8 (High)
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 , < a84d30e8d2bacd21782a6481158b7c9c552f4868
(git)
Affected: 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 , < 821807c167b7b48a41b95b6607c6b9f97600f7d9 (git) Affected: 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 , < 949d71666e9dd19f21e7b4b53a88cd2c5b902858 (git) Affected: 0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15 , < 75ed00055c059dedc47b5daaaa2f8a7a019138ff (git) |
guessed | |
| Linux | Linux |
Affected:
5.0
Unaffected: 0 , < 5.0 (semver) Unaffected: 6.12.75 , ≤ 6.12.* (semver) Unaffected: 6.18.14 , ≤ 6.18.* (semver) Unaffected: 6.19.4 , ≤ 6.19.* (semver) Unaffected: 7.0 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/iommu/intel/pasid.c",
"drivers/iommu/intel/pasid.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a84d30e8d2bacd21782a6481158b7c9c552f4868",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "821807c167b7b48a41b95b6607c6b9f97600f7d9",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "949d71666e9dd19f21e7b4b53a88cd2c5b902858",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "75ed00055c059dedc47b5daaaa2f8a7a019138ff",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/iommu/intel/pasid.c",
"drivers/iommu/intel/pasid.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.0"
},
{
"lessThan": "5.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.75",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.75",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.14",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0",
"versionStartIncluding": "5.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Clear Present bit before tearing down PASID entry\n\nThe Intel VT-d Scalable Mode PASID table entry consists of 512 bits (64\nbytes). When tearing down an entry, the current implementation zeros the\nentire 64-byte structure immediately using multiple 64-bit writes.\n\nSince the IOMMU hardware may fetch these 64 bytes using multiple\ninternal transactions (e.g., four 128-bit bursts), updating or zeroing\nthe entire entry while it is active (P=1) risks a \"torn\" read. If a\nhardware fetch occurs simultaneously with the CPU zeroing the entry, the\nhardware could observe an inconsistent state, leading to unpredictable\nbehavior or spurious faults.\n\nFollow the \"Guidance to Software for Invalidations\" in the VT-d spec\n(Section 6.5.3.3) by implementing the recommended ownership handshake:\n\n1. Clear only the \u0027Present\u0027 (P) bit of the PASID entry.\n2. Use a dma_wmb() to ensure the cleared bit is visible to hardware\n before proceeding.\n3. Execute the required invalidation sequence (PASID cache, IOTLB, and\n Device-TLB flush) to ensure the hardware has released all cached\n references.\n4. Only after the flushes are complete, zero out the remaining fields\n of the PASID entry.\n\nAlso, add a dma_wmb() in pasid_set_present() to ensure that all other\nfields of the PASID entry are visible to the hardware before the Present\nbit is set."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The teardown path is reached only through local interfaces \u2014 IOMMU domain attach/detach, SVA bind/unbind via accelerator char devices, and VFIO/iommufd ioctls \u2014 plus a locally-controlled device\u0027s DMA; there is no remote/network path to this code.\nAC:H - Triggering the torn read requires the IOMMU\u0027s internal multi-burst fetch of the 64-byte entry to interleave with the CPU\u0027s eight 64-bit zeroing writes during the narrow teardown window; this sub-microsecond hardware-internal timing is beyond the attacker\u0027s control and cannot be reliably reproduced.\nPR:L - Reaching the teardown requires local access to manage an IOMMU domain or to bind/unbind a PASID on an SVA-capable accelerator (reachable by an unprivileged user granted device access), not a pre-auth or fully unauthenticated path.\nUI:N - No victim interaction is needed; the attacker drives both the device DMA and the PASID-entry teardown.\nS:C - The IOMMU enforces the DMA isolation boundary; a torn/inconsistent PASID-entry read can cause the IOMMU to mistranslate a device\u0027s DMA, allowing access outside the device\u0027s authorized memory scope \u2014 an IOMMU/DMA boundary crossing.\nC:H - Mistranslation from an inconsistent entry read could let a device (e.g., guest-assigned or SVA-bound) read host physical memory outside its domain, yielding disclosure of memory beyond its authorized scope.\nI:H - The same mistranslation could let a device perform DMA writes to host physical memory outside its assigned domain, corrupting memory across the isolation boundary.\nA:H - The torn read causes \"spurious faults\" and \"unpredictable\" IOMMU behavior, which can produce DMA fault storms or device/translation failures impacting availability."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T12:28:39.976Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/a84d30e8d2bacd21782a6481158b7c9c552f4868"
},
{
"url": "https://git.kernel.org/stable/c/821807c167b7b48a41b95b6607c6b9f97600f7d9"
},
{
"url": "https://git.kernel.org/stable/c/949d71666e9dd19f21e7b4b53a88cd2c5b902858"
},
{
"url": "https://git.kernel.org/stable/c/75ed00055c059dedc47b5daaaa2f8a7a019138ff"
}
],
"title": "iommu/vt-d: Clear Present bit before tearing down PASID entry",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-45894",
"datePublished": "2026-05-27T12:17:04.866Z",
"dateReserved": "2026-05-13T15:03:33.083Z",
"dateUpdated": "2026-08-05T12:28:39.976Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-45894",
"date": "2026-10-04",
"epss": "0.00149",
"percentile": "0.0351"
},
"microsoft_vex": {
"current_release_date": "2026-09-24T02:29:42.000Z",
"cve": "CVE-2026-45894",
"id": "msrc_CVE-2026-45894",
"initial_release_date": "2026-05-28T01:04:10.000Z",
"product_status:known_affected": "8",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "iommu/vt-d: Clear Present bit before tearing down PASID entry",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-45894.json",
"version": "11"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/iommu/intel/pasid.c",
"drivers/iommu/intel/pasid.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a84d30e8d2bacd21782a6481158b7c9c552f4868",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "821807c167b7b48a41b95b6607c6b9f97600f7d9",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "949d71666e9dd19f21e7b4b53a88cd2c5b902858",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
},
{
"lessThan": "75ed00055c059dedc47b5daaaa2f8a7a019138ff",
"status": "affected",
"version": "0bbeb01a4fafbf8422e5c8882d461d6ac4f71e15",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/iommu/intel/pasid.c",
"drivers/iommu/intel/pasid.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.0"
},
{
"lessThan": "5.0",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.75",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.14",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.19.*",
"status": "unaffected",
"version": "6.19.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.0",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "458DA2B3-ABC5-462C-B5EE-93B1A52049FF",
"versionEndExcluding": "6.12.75",
"versionStartIncluding": "5.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "BF463CB7-1F58-4607-B847-77ED23E4B9B7",
"versionEndExcluding": "6.18.14",
"versionStartIncluding": "6.13",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "672A3E79-EC03-479D-8503-361DFBDC8092",
"versionEndExcluding": "6.19.4",
"versionStartIncluding": "6.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Clear Present bit before tearing down PASID entry\n\nThe Intel VT-d Scalable Mode PASID table entry consists of 512 bits (64\nbytes). When tearing down an entry, the current implementation zeros the\nentire 64-byte structure immediately using multiple 64-bit writes.\n\nSince the IOMMU hardware may fetch these 64 bytes using multiple\ninternal transactions (e.g., four 128-bit bursts), updating or zeroing\nthe entire entry while it is active (P=1) risks a \"torn\" read. If a\nhardware fetch occurs simultaneously with the CPU zeroing the entry, the\nhardware could observe an inconsistent state, leading to unpredictable\nbehavior or spurious faults.\n\nFollow the \"Guidance to Software for Invalidations\" in the VT-d spec\n(Section 6.5.3.3) by implementing the recommended ownership handshake:\n\n1. Clear only the \u0027Present\u0027 (P) bit of the PASID entry.\n2. Use a dma_wmb() to ensure the cleared bit is visible to hardware\n before proceeding.\n3. Execute the required invalidation sequence (PASID cache, IOTLB, and\n Device-TLB flush) to ensure the hardware has released all cached\n references.\n4. Only after the flushes are complete, zero out the remaining fields\n of the PASID entry.\n\nAlso, add a dma_wmb() in pasid_set_present() to ensure that all other\nfields of the PASID entry are visible to the hardware before the Present\nbit is set."
}
],
"id": "CVE-2026-45894",
"lastModified": "2026-06-25T21:10:07.130",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.1,
"impactScore": 6.0,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-05-27T14:17:03.610",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/75ed00055c059dedc47b5daaaa2f8a7a019138ff"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/821807c167b7b48a41b95b6607c6b9f97600f7d9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/949d71666e9dd19f21e7b4b53a88cd2c5b902858"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/a84d30e8d2bacd21782a6481158b7c9c552f4868"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-09-24T03:38:31+00:00",
"cve": "CVE-2026-45894",
"id": "CVE-2026-45894",
"initial_release_date": "2026-05-27T00:00:00+00:00",
"product_status:fixed": "762",
"product_status:known_affected": "22",
"product_status:known_not_affected": "42",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: iommu/vt-d: Clear Present bit before tearing down PASID entry",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45894.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-10-01T01:14:34Z",
"cve": "CVE-2026-45894",
"id": "CVE-2026-45894",
"initial_release_date": "2026-05-28T03:56:42Z",
"product_status:known_affected": "580",
"product_status:known_not_affected": "125",
"product_status:recommended": "320",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-45894",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-45894.json",
"version": "17"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…