https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 06:30:33 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-07254 bdu:2025-07254 https://cve.radiocsirt.org/vuln/bdu:2025-07254 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363 certfr-2024-avi-0363 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363 https://cve.radiocsirt.org/vuln/euvd-2026-344364 EUVD-2026-344364 https://cve.radiocsirt.org/vuln/euvd-2026-344364 https://cve.radiocsirt.org/vuln/fkie_cve-2021-47035 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/vt-d: Remove WO permissions on second-level paging entries</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/vt-d: Remove WO permissions on second-level paging entries</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-47035 https://cve.radiocsirt.org/vuln/ghsa-qp35-683c-hfxv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/vt-d: Remove WO permissions on second-level paging entries</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iommu/vt-d: Remove WO permissions on second-level paging entries</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> https://cve.radiocsirt.org/vuln/ghsa-qp35-683c-hfxv https://cve.radiocsirt.org/vuln/gsd-2021-47035 gsd-2021-47035 https://cve.radiocsirt.org/vuln/gsd-2021-47035 https://cve.radiocsirt.org/vuln/suse-su-2024:1465-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:1465-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47035 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 54 more</p> <p>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&#39;t want things to work sometimes, and break if we use 2nd level for the same mappings. Hence remove this configuration.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47035