<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 16:23:24 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</link>
      <description>CERTFR-2025-AVI-0895</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</guid>
    </item>
    <item>
      <title>bdu:2026-06021</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-06021</link>
      <description>bdu:2026-06021</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-06021</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53383</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2023-53383</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53383</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53383</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4&lt;/p&gt;
&lt;p&gt;The T241 platform suffers from the T241-FABRIC-4 erratum which causes
unexpected behavior in the GIC when multiple transactions are received
simultaneously from different sources. This hardware issue impacts
NVIDIA server platforms that use more than two T241 chips
interconnected. Each chip has support for 320 {E}SPIs.&lt;/p&gt;
&lt;p&gt;This issue occurs when multiple packets from different GICs are
incorrectly interleaved at the target chip. The erratum text below
specifies exactly what can cause multiple transfer packets susceptible
to interleaving and GIC state corruption. GIC state corruption can
lead to a range of problems, including kernel panics, and unexpected
behavior.&lt;/p&gt;
&lt;p&gt;&amp;gt;From the erratum text:
  &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple
  transfers, may be interleaved by the fabric when presented to ARM
  Generic Interrupt Controller. GIC expects all transfers of a packet
  to be delivered without any interleaving.&lt;/p&gt;
&lt;p&gt;The following GICv3 commands may result in multiple transfer packets
  over inter-socket AXI4 Stream interface:
   - Register reads from GICD_I* and GICD_N*
   - Register writes to 64-bit GICD registers other than GICD_IROUTERn*
   - ITS command MOVALL&lt;/p&gt;
&lt;p&gt;Multiple commands in GICv4+ utilize multiple transfer packets,
  including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;&lt;/p&gt;
&lt;p&gt;This issue impacts system configuration…&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/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4&lt;/p&gt;
&lt;p&gt;The T241 platform suffers from the T241-FABRIC-4 erratum which causes
unexpected behavior in the GIC when multiple transactions are received
simultaneously from different sources. This hardware issue impacts
NVIDIA server platforms that use more than two T241 chips
interconnected. Each chip has support for 320 {E}SPIs.&lt;/p&gt;
&lt;p&gt;This issue occurs when multiple packets from different GICs are
incorrectly interleaved at the target chip. The erratum text below
specifies exactly what can cause multiple transfer packets susceptible
to interleaving and GIC state corruption. GIC state corruption can
lead to a range of problems, including kernel panics, and unexpected
behavior.&lt;/p&gt;
&lt;p&gt;&amp;gt;From the erratum text:
  &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple
  transfers, may be interleaved by the fabric when presented to ARM
  Generic Interrupt Controller. GIC expects all transfers of a packet
  to be delivered without any interleaving.&lt;/p&gt;
&lt;p&gt;The following GICv3 commands may result in multiple transfer packets
  over inter-socket AXI4 Stream interface:
   - Register reads from GICD_I* and GICD_N*
   - Register writes to 64-bit GICD registers other than GICD_IROUTERn*
   - ITS command MOVALL&lt;/p&gt;
&lt;p&gt;Multiple commands in GICv4+ utilize multiple transfer packets,
  including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;&lt;/p&gt;
&lt;p&gt;This issue impacts system configuration…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53383</guid>
    </item>
    <item>
      <title>GHSA-pg59-r5p5-6cfh</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pg59-r5p5-6cfh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4&lt;/p&gt;
&lt;p&gt;The T241 platform suffers from the T241-FABRIC-4 erratum which causes
unexpected behavior in the GIC when multiple transactions are received
simultaneously from different sources. This hardware issue impacts
NVIDIA server platforms that use more than two T241 chips
interconnected. Each chip has support for 320 {E}SPIs.&lt;/p&gt;
&lt;p&gt;This issue occurs when multiple packets from different GICs are
incorrectly interleaved at the target chip. The erratum text below
specifies exactly what can cause multiple transfer packets susceptible
to interleaving and GIC state corruption. GIC state corruption can
lead to a range of problems, including kernel panics, and unexpected
behavior.&lt;/p&gt;
&lt;p&gt;&amp;gt;From the erratum text:
  &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple
  transfers, may be interleaved by the fabric when presented to ARM
  Generic Interrupt Controller. GIC expects all transfers of a packet
  to be delivered without any interleaving.&lt;/p&gt;
&lt;p&gt;The following GICv3 commands may result in multiple transfer packets
  over inter-socket AXI4 Stream interface:
   - Register reads from GICD_I* and GICD_N*
   - Register writes to 64-bit GICD registers other than GICD_IROUTERn*
   - ITS command MOVALL&lt;/p&gt;
&lt;p&gt;Multiple commands in GICv4+ utilize multiple transfer packets,
  including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;&lt;/p&gt;
&lt;p&gt;This issue impacts system configuration…&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/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4&lt;/p&gt;
&lt;p&gt;The T241 platform suffers from the T241-FABRIC-4 erratum which causes
unexpected behavior in the GIC when multiple transactions are received
simultaneously from different sources. This hardware issue impacts
NVIDIA server platforms that use more than two T241 chips
interconnected. Each chip has support for 320 {E}SPIs.&lt;/p&gt;
&lt;p&gt;This issue occurs when multiple packets from different GICs are
incorrectly interleaved at the target chip. The erratum text below
specifies exactly what can cause multiple transfer packets susceptible
to interleaving and GIC state corruption. GIC state corruption can
lead to a range of problems, including kernel panics, and unexpected
behavior.&lt;/p&gt;
&lt;p&gt;&amp;gt;From the erratum text:
  &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple
  transfers, may be interleaved by the fabric when presented to ARM
  Generic Interrupt Controller. GIC expects all transfers of a packet
  to be delivered without any interleaving.&lt;/p&gt;
&lt;p&gt;The following GICv3 commands may result in multiple transfer packets
  over inter-socket AXI4 Stream interface:
   - Register reads from GICD_I* and GICD_N*
   - Register writes to 64-bit GICD registers other than GICD_IROUTERn*
   - ITS command MOVALL&lt;/p&gt;
&lt;p&gt;Multiple commands in GICv4+ utilize multiple transfer packets,
  including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;&lt;/p&gt;
&lt;p&gt;This issue impacts system configuration…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pg59-r5p5-6cfh</guid>
    </item>
    <item>
      <title>msrc_CVE-2023-53383 — irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2023-53383</link>
      <description>msrc_CVE-2023-53383</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2023-53383</guid>
    </item>
    <item>
      <title>RHSA-2023:5069 — security update for kernel</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:5069</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:5069</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03615-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:03615-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://vulnerability.circl.lu/vuln/suse-su-2025:03615-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53383</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53383</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 170 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 The T241 platform suffers from the T241-FABRIC-4 erratum which causes unexpected behavior in the GIC when multiple transactions are received simultaneously from different sources. This hardware issue impacts NVIDIA server platforms that use more than two T241 chips interconnected. Each chip has support for 320 {E}SPIs. This issue occurs when multiple packets from different GICs are incorrectly interleaved at the target chip. The erratum text below specifies exactly what can cause multiple transfer packets susceptible to interleaving and GIC state corruption. GIC state corruption can lead to a range of problems, including kernel panics, and unexpected behavior. &amp;gt;From the erratum text:   &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple   transfers, may be interleaved by the fabric when presented to ARM   Generic Interrupt Controller. GIC expects all transfers of a packet   to be delivered without any interleaving.   The following GICv3 commands may result in multiple transfer packets   over inter-socket AXI4 Stream interface:    - Register reads from GICD_I* and GICD_N*    - Register writes to 64-bit GICD registers other than GICD_IROUTERn*    - ITS command MOVALL   Multiple commands in GICv4+ utilize multiple transfer packets,   including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;   This issue impacts system configurations with…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 170 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 The T241 platform suffers from the T241-FABRIC-4 erratum which causes unexpected behavior in the GIC when multiple transactions are received simultaneously from different sources. This hardware issue impacts NVIDIA server platforms that use more than two T241 chips interconnected. Each chip has support for 320 {E}SPIs. This issue occurs when multiple packets from different GICs are incorrectly interleaved at the target chip. The erratum text below specifies exactly what can cause multiple transfer packets susceptible to interleaving and GIC state corruption. GIC state corruption can lead to a range of problems, including kernel panics, and unexpected behavior. &amp;gt;From the erratum text:   &amp;#34;In some cases, inter-socket AXI4 Stream packets with multiple   transfers, may be interleaved by the fabric when presented to ARM   Generic Interrupt Controller. GIC expects all transfers of a packet   to be delivered without any interleaving.   The following GICv3 commands may result in multiple transfer packets   over inter-socket AXI4 Stream interface:    - Register reads from GICD_I* and GICD_N*    - Register writes to 64-bit GICD registers other than GICD_IROUTERn*    - ITS command MOVALL   Multiple commands in GICv4+ utilize multiple transfer packets,   including VMOVP, VMOVI, VMAPP, and 64-bit register accesses.&amp;#34;   This issue impacts system configurations with…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53383</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2092 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2092</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2092</guid>
    </item>
  </channel>
</rss>
