CVE-2021-47035

iommu/vt-d: Remove WO permissions on second-level paging entries

MEDIUM
5.5
CVSS Score
Published: February 28, 2024 at 08:13 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.11.215.12 ≤ v < 5.12.45.6 ≤ v < 5.10.375.6 ≤ v < 5.10.385.6 ≤ v < 5.11.215.6 ≤ v < 5.12.45.6 ≤ v < 5.135.6b802d070a52a1565b47daaa808872cfbd4a17b01
Vendor states this is fixed in 25faff78138933244c678c7fc78f7c0340fa04a0 (fixed)
Vendor states this is fixed in 66c24699f266ff310381a9552d3576eea8ad6e20 (fixed)
Vendor states this is fixed in 89bd620798704a8805fc9db0d71d7f812cf5b3d2 (fixed)
Vendor states this is fixed in eea53c5816889ee8b64544fa2e9311a81184ff9c (fixed)
Affected range stops below 5.10.37, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.38 (unaffected)
Vendor states this is fixed in 5.11.21 (unaffected)
Vendor states this is fixed in 5.12.4 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/25faff78138933244c678c7fc78f7c0340fa04a0
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/66c24699f266ff310381a9552d3576eea8ad6e20
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/89bd620798704a8805fc9db0d71d7f812cf5b3d2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/eea53c5816889ee8b64544fa2e9311a81184ff9c
Patch
Source: af854a3a-2127-422b-91ae-364da2661108
https://git.kernel.org/stable/c/c848416cc05afc1589edba04fe00b85c2f797ee3

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card