<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 04:08:51 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38216</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-38216</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0625 — De multiples vulnérabilités ont été découvertes dans Ubuntu Ubuntu. Certaines d'entre elles permettent à un attaquant d…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</link>
      <description>certfr-2025-avi-0625</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0625</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38216</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38216</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Restore context entry setup order for aliased devices Commit 2031c469f816 (&amp;#34;iommu/vt-d: Add support for static identity domain&amp;#34;) changed the context entry setup during domain attachment from a set-and-check policy to a clear-and-reset approach. This inadvertently introduced a regression affecting PCI aliased devices behind PCIe-to-PCI bridges. Specifically, keyboard and touchpad stopped working on several Apple Macbooks with below messages:  kernel: platform pxa2xx-spi.3: Adding to iommu group 20  kernel: input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:1e.3/pxa2xx-spi.3/spi_master/spi2/spi-APP000D:00/input/input0  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: DMAR: DRHD: handling fault status reg 3  kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00 Fix this by restoring the previous context setup order.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 82 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Restore context entry setup order for aliased devices Commit 2031c469f816 (&amp;#34;iommu/vt-d: Add support for static identity domain&amp;#34;) changed the context entry setup during domain attachment from a set-and-check policy to a clear-and-reset approach. This inadvertently introduced a regression affecting PCI aliased devices behind PCIe-to-PCI bridges. Specifically, keyboard and touchpad stopped working on several Apple Macbooks with below messages:  kernel: platform pxa2xx-spi.3: Adding to iommu group 20  kernel: input: Apple SPI Keyboard as /devices/pci0000:00/0000:00:1e.3/pxa2xx-spi.3/spi_master/spi2/spi-APP000D:00/input/input0  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00  kernel: DMAR: DRHD: handling fault status reg 3  kernel: DMAR: [DMA Read NO_PASID] Request device [00:1e.3] fault addr  0xffffa000 [fault reason 0x06] PTE Read access is not set  kernel: DMAR: DRHD: handling fault status reg 3  kernel: applespi spi-APP000D:00: Error writing to device: 01 0e 00 00 Fix this by restoring the previous context setup order.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38216</guid>
    </item>
  </channel>
</rss>
