Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2021-47035

UNKNOWN
Published 2024-02-28T08:13:43.404Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2021-47035. We'll provide specific mitigation strategies based on your environment and risk profile.

No CVSS data available

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

Linux

Linux

Affected Versions:

b802d070a52a1565b47daaa808872cfbd4a17b01 b802d070a52a1565b47daaa808872cfbd4a17b01 b802d070a52a1565b47daaa808872cfbd4a17b01 b802d070a52a1565b47daaa808872cfbd4a17b01
Linux

Linux

Affected Versions:

5.6 0 5.10.38 5.11.21 5.12.4 5.13

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

⚠ Unreviewed MODERATE

GHSA-qp35-683c-hfxv

Advisory Details

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.

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References

ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2021-47035
WEB https://git.kernel.org/stable/c/25faff78138933244c678c7fc78f7c0340fa04a0
WEB https://git.kernel.org/stable/c/66c24699f266ff310381a9552d3576eea8ad6e20
WEB https://git.kernel.org/stable/c/89bd620798704a8805fc9db0d71d7f812cf5b3d2
WEB https://git.kernel.org/stable/c/c848416cc05afc1589edba04fe00b85c2f797ee3
WEB https://git.kernel.org/stable/c/eea53c5816889ee8b64544fa2e9311a81184ff9c

Advisory provided by GitHub Security Advisory Database. Published: February 28, 2024, Modified: January 9, 2025

References

https://git.kernel.org/stable/c/89bd620798704a8805fc9db0d71d7f812cf5b3d2
https://git.kernel.org/stable/c/25faff78138933244c678c7fc78f7c0340fa04a0
https://git.kernel.org/stable/c/66c24699f266ff310381a9552d3576eea8ad6e20
https://git.kernel.org/stable/c/eea53c5816889ee8b64544fa2e9311a81184ff9c
Published: 2024-02-28T08:13:43.404Z
Last Modified: 2025-05-04T07:02:44.368Z
Copied to clipboard!