CVE-2021-47035
published 2024-02-28CVE-2021-47035: 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…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.26%
17.2th percentile
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
13 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.38-1 (bookworm) | linux 5.10.38-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= b802d070a52a1565b47daaa808872cfbd4a17b01 < 89bd620798704a8805fc9db0d71d7f812cf5b3d2 | 89bd620798704a8805fc9db0d71d7f812cf5b3d2 |
| linux | linux | >= b802d070a52a1565b47daaa808872cfbd4a17b01 < 25faff78138933244c678c7fc78f7c0340fa04a0 | 25faff78138933244c678c7fc78f7c0340fa04a0 |
| linux | linux | >= b802d070a52a1565b47daaa808872cfbd4a17b01 < 66c24699f266ff310381a9552d3576eea8ad6e20 | 66c24699f266ff310381a9552d3576eea8ad6e20 |
| linux | linux | >= b802d070a52a1565b47daaa808872cfbd4a17b01 < eea53c5816889ee8b64544fa2e9311a81184ff9c | eea53c5816889ee8b64544fa2e9311a81184ff9c |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 5.11 < 5.11.21 | 5.11.21 |
| linux | linux_kernel | >= 5.12 < 5.12.4 | 5.12.4 |
| linux | linux_kernel | >= 5.6 < 5.10.37 | 5.10.37 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: iommu/vt-d: Remove WO permissions on second-level paging entries
vendor_redhat·2024-02-28·CVSS 5.5
CVE-2021-47035 [MEDIUM] CWE-20 kernel: iommu/vt-d: Remove WO permissions on second-level paging entries
kernel: iommu/vt-d: Remove WO permissions on second-level paging entries
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.
Package: kernel (Red Hat Enterprise Linux 6) - Out of sup
Debian
CVE-2021-47035: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d:...
vendor_debian·2021·CVSS 5.5
CVE-2021-47035 [MEDIUM] CVE-2021-47035: linux - In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d:...
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.
Scope: local
bookworm: resolved (fixed in 5.10.38-1)
bullseye: resolved (fixed in 5.10.38-1)
forky: resolved (fixed in 5.10.38-1)
si
GHSA
GHSA-qp35-683c-hfxv: In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Remove WO permissions on second-level paging entries
When the first
ghsa_unreviewed·2024-02-28
CVE-2021-47035 [MEDIUM] GHSA-qp35-683c-hfxv: In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Remove WO permissions on second-level paging entries
When the first
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.
OSV
CVE-2021-47035: In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Remove WO permissions on second-level paging entries When the first le
osv·2024-02-28·CVSS 5.5
CVE-2021-47035 [MEDIUM] CVE-2021-47035: In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Remove WO permissions on second-level paging entries When the first le
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/25faff78138933244c678c7fc78f7c0340fa04a0https://git.kernel.org/stable/c/66c24699f266ff310381a9552d3576eea8ad6e20https://git.kernel.org/stable/c/89bd620798704a8805fc9db0d71d7f812cf5b3d2https://git.kernel.org/stable/c/eea53c5816889ee8b64544fa2e9311a81184ff9chttps://git.kernel.org/stable/c/25faff78138933244c678c7fc78f7c0340fa04a0https://git.kernel.org/stable/c/66c24699f266ff310381a9552d3576eea8ad6e20https://git.kernel.org/stable/c/89bd620798704a8805fc9db0d71d7f812cf5b3d2https://git.kernel.org/stable/c/c848416cc05afc1589edba04fe00b85c2f797ee3https://git.kernel.org/stable/c/eea53c5816889ee8b64544fa2e9311a81184ff9c
2024-02-28
Published