<?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://cve.radiocsirt.org</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, 03 Oct 2026 11:21:56 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-11566</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11566</link>
      <description>bdu:2026-11566</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11566</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23085</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23085</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-23085</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-326697</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326697</link>
      <description>EUVD-2026-326697</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326697</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23085</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23085</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gic-v3-its: Avoid truncating memory addresses&lt;/p&gt;
&lt;p&gt;On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem
allocations to be backed by addresses physical memory above the 32-bit
address limit, as found while experimenting with larger VMSPLIT
configurations.&lt;/p&gt;
&lt;p&gt;This caused the qemu virt model to crash in the GICv3 driver, which
allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below
the 4GB physical address limit is in ZONE_DMA in this configuration,
kmalloc() defaults to higher addresses for ZONE_NORMAL, and the
ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39;
variable.&lt;/p&gt;
&lt;p&gt;Change the itt_addr variable to the correct phys_addr_t type instead,
along with all other variables in this driver that hold a physical
address.&lt;/p&gt;
&lt;p&gt;The gicv5 driver correctly uses u64 variables, while all other irqchip
drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that
other device drivers have similar issues, but fixing this one is
sufficient for booting a virtio based guest.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gic-v3-its: Avoid truncating memory addresses&lt;/p&gt;
&lt;p&gt;On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem
allocations to be backed by addresses physical memory above the 32-bit
address limit, as found while experimenting with larger VMSPLIT
configurations.&lt;/p&gt;
&lt;p&gt;This caused the qemu virt model to crash in the GICv3 driver, which
allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below
the 4GB physical address limit is in ZONE_DMA in this configuration,
kmalloc() defaults to higher addresses for ZONE_NORMAL, and the
ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39;
variable.&lt;/p&gt;
&lt;p&gt;Change the itt_addr variable to the correct phys_addr_t type instead,
along with all other variables in this driver that hold a physical
address.&lt;/p&gt;
&lt;p&gt;The gicv5 driver correctly uses u64 variables, while all other irqchip
drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that
other device drivers have similar issues, but fixing this one is
sufficient for booting a virtio based guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23085</guid>
    </item>
    <item>
      <title>GHSA-v2xc-c9fw-v73w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v2xc-c9fw-v73w</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gic-v3-its: Avoid truncating memory addresses&lt;/p&gt;
&lt;p&gt;On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem
allocations to be backed by addresses physical memory above the 32-bit
address limit, as found while experimenting with larger VMSPLIT
configurations.&lt;/p&gt;
&lt;p&gt;This caused the qemu virt model to crash in the GICv3 driver, which
allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below
the 4GB physical address limit is in ZONE_DMA in this configuration,
kmalloc() defaults to higher addresses for ZONE_NORMAL, and the
ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39;
variable.&lt;/p&gt;
&lt;p&gt;Change the itt_addr variable to the correct phys_addr_t type instead,
along with all other variables in this driver that hold a physical
address.&lt;/p&gt;
&lt;p&gt;The gicv5 driver correctly uses u64 variables, while all other irqchip
drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that
other device drivers have similar issues, but fixing this one is
sufficient for booting a virtio based guest.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gic-v3-its: Avoid truncating memory addresses&lt;/p&gt;
&lt;p&gt;On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem
allocations to be backed by addresses physical memory above the 32-bit
address limit, as found while experimenting with larger VMSPLIT
configurations.&lt;/p&gt;
&lt;p&gt;This caused the qemu virt model to crash in the GICv3 driver, which
allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below
the 4GB physical address limit is in ZONE_DMA in this configuration,
kmalloc() defaults to higher addresses for ZONE_NORMAL, and the
ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39;
variable.&lt;/p&gt;
&lt;p&gt;Change the itt_addr variable to the correct phys_addr_t type instead,
along with all other variables in this driver that hold a physical
address.&lt;/p&gt;
&lt;p&gt;The gicv5 driver correctly uses u64 variables, while all other irqchip
drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that
other device drivers have similar issues, but fixing this one is
sufficient for booting a virtio based guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v2xc-c9fw-v73w</guid>
    </item>
    <item>
      <title>OESA-2026-1469 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the &amp;amp;apos;itt&amp;amp;apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit &amp;amp;apos;unsigned long&amp;amp;apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the &amp;amp;apos;itt&amp;amp;apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit &amp;amp;apos;unsigned long&amp;amp;apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1469</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:20416-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:20416-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0962-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:0962-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23085</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23085</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39; variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that other device drivers have similar issues, but fixing this one is sufficient for booting a virtio based guest.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 230 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Avoid truncating memory addresses On 32-bit machines with CONFIG_ARM_LPAE, it is possible for lowmem allocations to be backed by addresses physical memory above the 32-bit address limit, as found while experimenting with larger VMSPLIT configurations. This caused the qemu virt model to crash in the GICv3 driver, which allocates the &amp;#39;itt&amp;#39; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses for ZONE_NORMAL, and the ITS driver stores the physical address in a 32-bit &amp;#39;unsigned long&amp;#39; variable. Change the itt_addr variable to the correct phys_addr_t type instead, along with all other variables in this driver that hold a physical address. The gicv5 driver correctly uses u64 variables, while all other irqchip drivers don&amp;#39;t call virt_to_phys or similar interfaces. It&amp;#39;s expected that other device drivers have similar issues, but fixing this one is sufficient for booting a virtio based guest.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23085</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0324 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0324</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0324</guid>
    </item>
  </channel>
</rss>
