Answer in brief
CVE-2021-47035 records a High severity (CVSS 8.8) vulnerability in iommu/vt-d: Remove WO permissions on second-level paging entries. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b802d070a52a1565b47daaa808872cfbd4a17b01 <89bd620798704a8805fc9db0d71d7f812cf5b3d2 || >=b802d070a52a1565b47daaa808872cfbd4a17b01 <25faff78138933244c678c7fc78f7c0340fa04a0 || >=b802d070a52a1565b47daaa808872cfbd4a17b01 <66c24699f266ff310381a9552d3576eea8ad6e20 || >=b802d070a52a1565b47daaa808872cfbd4a17b01 <eea53c5816889ee8b64544fa2e9311a81184ff9c | 89bd620798704a8805fc9db0d71d7f812cf5b3d2, 25faff78138933244c678c7fc78f7c0340fa04a0, 66c24699f266ff310381a9552d3576eea8ad6e20, eea53c5816889ee8b64544fa2e9311a81184ff9c |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Feb 28, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Remove WO permissions on second-level paging entries When the first level page table is used for IOVA translation, it only supports Read-Only and Read-Write permissions. The Write-Only permission is not supported as the PRESENT bit (implying Read permission) should always set. When using second level, we still give separate permissions that allows WriteOnly which seems inconsistent and awkward. We want to have consistent behavior. After moving to 1st level, we don't want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.
Quoted source text, attributed separately from HOL analysis.