<?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>Fri, 02 Oct 2026 23:31:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14059</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-14059</link>
      <description>bdu:2026-14059</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-14059</guid>
    </item>
    <item>
      <title>Withdrawn: BELL-CVE-2026-53243 — CVE-2026-53243 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53243</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53243</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>EUVD-2026-330100</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-330100</link>
      <description>EUVD-2026-330100</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-330100</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53243</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53243</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()&lt;/p&gt;
&lt;p&gt;There is an bug in which an uninitialized stack variable is used in
rseq_exit_user_update() as reported by syzbot:&lt;/p&gt;
&lt;p&gt;BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]&lt;/p&gt;
&lt;p&gt;The local variable:&lt;/p&gt;
&lt;p&gt;struct rseq_ids ids = {
		.cpu_id	 = task_cpu(t),
		.mm_cid	 = task_mm_cid(t),
		.node_id = cpu_to_node(ids.cpu_id),
	};&lt;/p&gt;
&lt;p&gt;According to the C standard, the evaluation order of expressions in an
initializer list is indeterminately sequenced. The compiler (Clang, in
this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*
`ids.cpu_id` is initialized with `task_cpu(t)`.&lt;/p&gt;
&lt;p&gt;This is fixed by moving the assignment of ids.node_id outside the
structure initialization.&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;rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()&lt;/p&gt;
&lt;p&gt;There is an bug in which an uninitialized stack variable is used in
rseq_exit_user_update() as reported by syzbot:&lt;/p&gt;
&lt;p&gt;BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]&lt;/p&gt;
&lt;p&gt;The local variable:&lt;/p&gt;
&lt;p&gt;struct rseq_ids ids = {
		.cpu_id	 = task_cpu(t),
		.mm_cid	 = task_mm_cid(t),
		.node_id = cpu_to_node(ids.cpu_id),
	};&lt;/p&gt;
&lt;p&gt;According to the C standard, the evaluation order of expressions in an
initializer list is indeterminately sequenced. The compiler (Clang, in
this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*
`ids.cpu_id` is initialized with `task_cpu(t)`.&lt;/p&gt;
&lt;p&gt;This is fixed by moving the assignment of ids.node_id outside the
structure initialization.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53243</guid>
    </item>
    <item>
      <title>GHSA-qhcg-6255-c538</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qhcg-6255-c538</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()&lt;/p&gt;
&lt;p&gt;There is an bug in which an uninitialized stack variable is used in
rseq_exit_user_update() as reported by syzbot:&lt;/p&gt;
&lt;p&gt;BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]&lt;/p&gt;
&lt;p&gt;The local variable:&lt;/p&gt;
&lt;p&gt;struct rseq_ids ids = {
		.cpu_id	 = task_cpu(t),
		.mm_cid	 = task_mm_cid(t),
		.node_id = cpu_to_node(ids.cpu_id),
	};&lt;/p&gt;
&lt;p&gt;According to the C standard, the evaluation order of expressions in an
initializer list is indeterminately sequenced. The compiler (Clang, in
this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*
`ids.cpu_id` is initialized with `task_cpu(t)`.&lt;/p&gt;
&lt;p&gt;This is fixed by moving the assignment of ids.node_id outside the
structure initialization.&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;rseq: Fix using an uninitialized stack variable in rseq_exit_user_update()&lt;/p&gt;
&lt;p&gt;There is an bug in which an uninitialized stack variable is used in
rseq_exit_user_update() as reported by syzbot:&lt;/p&gt;
&lt;p&gt;BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline]&lt;/p&gt;
&lt;p&gt;The local variable:&lt;/p&gt;
&lt;p&gt;struct rseq_ids ids = {
		.cpu_id	 = task_cpu(t),
		.mm_cid	 = task_mm_cid(t),
		.node_id = cpu_to_node(ids.cpu_id),
	};&lt;/p&gt;
&lt;p&gt;According to the C standard, the evaluation order of expressions in an
initializer list is indeterminately sequenced. The compiler (Clang, in
this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before*
`ids.cpu_id` is initialized with `task_cpu(t)`.&lt;/p&gt;
&lt;p&gt;This is fixed by moving the assignment of ids.node_id outside the
structure initialization.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qhcg-6255-c538</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53243</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53243</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rseq: Fix using an uninitialized stack variable in rseq_exit_user_update() There is an bug in which an uninitialized stack variable is used in rseq_exit_user_update() as reported by syzbot: BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline] The local variable: 	struct rseq_ids ids = { 		.cpu_id	 = task_cpu(t), 		.mm_cid	 = task_mm_cid(t), 		.node_id = cpu_to_node(ids.cpu_id), 	}; According to the C standard, the evaluation order of expressions in an initializer list is indeterminately sequenced. The compiler (Clang, in this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before* `ids.cpu_id` is initialized with `task_cpu(t)`. This is fixed by moving the assignment of ids.node_id outside the structure initialization.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rseq: Fix using an uninitialized stack variable in rseq_exit_user_update() There is an bug in which an uninitialized stack variable is used in rseq_exit_user_update() as reported by syzbot: BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline] The local variable: 	struct rseq_ids ids = { 		.cpu_id	 = task_cpu(t), 		.mm_cid	 = task_mm_cid(t), 		.node_id = cpu_to_node(ids.cpu_id), 	}; According to the C standard, the evaluation order of expressions in an initializer list is indeterminately sequenced. The compiler (Clang, in this KMSAN build) evaluates `cpu_to_node(ids.cpu_id)` *before* `ids.cpu_id` is initialized with `task_cpu(t)`. This is fixed by moving the assignment of ids.node_id outside the structure initialization.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53243</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2077 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2077</guid>
    </item>
  </channel>
</rss>
