CVE-2021-47035: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2021-47035 is a vulnerability identified in the Linux kernel's IOMMU (Input-Output Memory Management Unit) implementation, specifically related to Intel VT-d (Virtualization Technology for Directed I/O) second-level paging entries. The issue arises from inconsistent permission handling in the page table entries used for IOVA (IO Virtual Address) translation. In the first-level page table, only Read-Only and Read-Write permissions are supported, with the Write-Only (WO) permission being invalid because the PRESENT bit, which implies read permission, must always be set. However, in the second-level page tables, the Linux kernel erroneously allowed Write-Only permissions, creating an inconsistency and potential security risk. This discrepancy could lead to unpredictable behavior or security flaws when the second-level paging entries are used for IOVA translation, potentially allowing unauthorized write access without proper read permissions. The patch removes the Write-Only permission configuration from second-level paging entries to enforce consistent permission handling across both levels, thereby mitigating the risk of exploitation. Although no known exploits are currently reported in the wild, the vulnerability affects the Linux kernel versions identified by the given commit hashes and pertains to systems utilizing Intel VT-d for device virtualization and memory isolation.
Potential Impact
For European organizations, the impact of CVE-2021-47035 primarily concerns environments that rely on Linux-based virtualization infrastructures, especially those using Intel VT-d for secure device assignment and memory isolation. This includes cloud service providers, data centers, and enterprises running virtualized workloads on Linux hosts. Exploitation could potentially allow malicious actors or compromised virtual machines to bypass memory access restrictions, leading to unauthorized write operations on memory regions. This could compromise the confidentiality and integrity of data, disrupt virtual machine isolation, and potentially lead to privilege escalation or denial of service. Given the widespread use of Linux in critical infrastructure, telecommunications, and enterprise IT across Europe, failure to address this vulnerability could expose sensitive systems to targeted attacks. However, the absence of known exploits and the technical complexity of exploiting this issue somewhat limit immediate risk, but the potential for future exploitation remains, especially in high-value environments.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that remove the Write-Only permission from second-level paging entries in the IOMMU VT-d implementation. This involves updating to the latest stable Linux kernel versions that include the fix referenced by the commit hashes. Additionally, organizations should audit their virtualization environments to identify systems using Intel VT-d and ensure they are running patched kernels. Employing strict access controls and monitoring for unusual IOMMU or virtualization-related activities can help detect attempts to exploit this vulnerability. For environments where immediate patching is challenging, consider isolating critical virtual machines and limiting device passthrough capabilities to reduce attack surface. Regularly reviewing kernel security advisories and maintaining an up-to-date vulnerability management process will also help mitigate risks associated with this and similar vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2021-47035: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2021-47035 is a vulnerability identified in the Linux kernel's IOMMU (Input-Output Memory Management Unit) implementation, specifically related to Intel VT-d (Virtualization Technology for Directed I/O) second-level paging entries. The issue arises from inconsistent permission handling in the page table entries used for IOVA (IO Virtual Address) translation. In the first-level page table, only Read-Only and Read-Write permissions are supported, with the Write-Only (WO) permission being invalid because the PRESENT bit, which implies read permission, must always be set. However, in the second-level page tables, the Linux kernel erroneously allowed Write-Only permissions, creating an inconsistency and potential security risk. This discrepancy could lead to unpredictable behavior or security flaws when the second-level paging entries are used for IOVA translation, potentially allowing unauthorized write access without proper read permissions. The patch removes the Write-Only permission configuration from second-level paging entries to enforce consistent permission handling across both levels, thereby mitigating the risk of exploitation. Although no known exploits are currently reported in the wild, the vulnerability affects the Linux kernel versions identified by the given commit hashes and pertains to systems utilizing Intel VT-d for device virtualization and memory isolation.
Potential Impact
For European organizations, the impact of CVE-2021-47035 primarily concerns environments that rely on Linux-based virtualization infrastructures, especially those using Intel VT-d for secure device assignment and memory isolation. This includes cloud service providers, data centers, and enterprises running virtualized workloads on Linux hosts. Exploitation could potentially allow malicious actors or compromised virtual machines to bypass memory access restrictions, leading to unauthorized write operations on memory regions. This could compromise the confidentiality and integrity of data, disrupt virtual machine isolation, and potentially lead to privilege escalation or denial of service. Given the widespread use of Linux in critical infrastructure, telecommunications, and enterprise IT across Europe, failure to address this vulnerability could expose sensitive systems to targeted attacks. However, the absence of known exploits and the technical complexity of exploiting this issue somewhat limit immediate risk, but the potential for future exploitation remains, especially in high-value environments.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that remove the Write-Only permission from second-level paging entries in the IOMMU VT-d implementation. This involves updating to the latest stable Linux kernel versions that include the fix referenced by the commit hashes. Additionally, organizations should audit their virtualization environments to identify systems using Intel VT-d and ensure they are running patched kernels. Employing strict access controls and monitoring for unusual IOMMU or virtualization-related activities can help detect attempts to exploit this vulnerability. For environments where immediate patching is challenging, consider isolating critical virtual machines and limiting device passthrough capabilities to reduce attack surface. Regularly reviewing kernel security advisories and maintaining an up-to-date vulnerability management process will also help mitigate risks associated with this and similar vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-27T18:42:55.964Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9834c4522896dcbe9b12
Added to database: 5/21/2025, 9:09:08 AM
Last enriched: 6/30/2025, 7:54:55 PM
Last updated: 10/16/2025, 12:44:40 PM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-9955: Vulnerability in WSO2 WSO2 Enterprise Integrator
MediumCVE-2025-10611: Vulnerability in WSO2 WSO2 API Manager
CriticalCVE-2025-58426: Use of hard-coded cryptographic key in NEOJAPAN Inc. desknet's NEO
MediumCVE-2025-58079: Improper Protection of Alternate Path in NEOJAPAN Inc. desknet's NEO
MediumCVE-2025-55072: Cross-site scripting (XSS) in NEOJAPAN Inc. desknet's NEO
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.