<?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:56:30 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:63128 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:63128</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)
  * kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)
  * kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)
  * kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)
  * kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)
  * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)
  * kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)
  * kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)
  * kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)
  * kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)
  * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:63128</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-63808</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-63808</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-63808</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957</link>
      <description>certfr-2026-avi-0957</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957</guid>
    </item>
    <item>
      <title>EUVD-2026-353130</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353130</link>
      <description>EUVD-2026-353130</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353130</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63808</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63808</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exfat: fix potential use-after-free in exfat_find_dir_entry()&lt;/p&gt;
&lt;p&gt;In exfat_find_dir_entry(), the buffer_head obtained from
exfat_get_dentry() is released with brelse(bh) before the fall-through
TYPE_EXTEND branch reads the directory entry through ep (which points
into bh-&amp;gt;b_data):&lt;/p&gt;
&lt;p&gt;brelse(bh);
	if (entry_type == TYPE_EXTEND) {
		...
		len = exfat_extract_uni_name(ep, entry_uniname);
		...
	}&lt;/p&gt;
&lt;p&gt;After brelse() drops our reference, nothing guarantees that the
underlying page backing bh-&amp;gt;b_data remains valid for the subsequent
exfat_extract_uni_name() read. This is the same pattern fixed in
commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in
exfat_load_upcase_table()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Move brelse(bh) so it runs after ep is no longer dereferenced on
each branch.&lt;/p&gt;
&lt;p&gt;Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image
(long filename with same-hash collisions forcing the TYPE_EXTEND path).
With a debug-only invalidate_bdev() inserted between brelse(bh) and
the ep read to make the stale-deref window deterministic, the
unpatched kernel faults:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0
  BUG: unable to handle page fault for address: ffff88801a5fa0c2
  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0&lt;/p&gt;
&lt;p&gt;With this patch applied, the same instrumented harness completes
clean…&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;exfat: fix potential use-after-free in exfat_find_dir_entry()&lt;/p&gt;
&lt;p&gt;In exfat_find_dir_entry(), the buffer_head obtained from
exfat_get_dentry() is released with brelse(bh) before the fall-through
TYPE_EXTEND branch reads the directory entry through ep (which points
into bh-&amp;gt;b_data):&lt;/p&gt;
&lt;p&gt;brelse(bh);
	if (entry_type == TYPE_EXTEND) {
		...
		len = exfat_extract_uni_name(ep, entry_uniname);
		...
	}&lt;/p&gt;
&lt;p&gt;After brelse() drops our reference, nothing guarantees that the
underlying page backing bh-&amp;gt;b_data remains valid for the subsequent
exfat_extract_uni_name() read. This is the same pattern fixed in
commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in
exfat_load_upcase_table()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Move brelse(bh) so it runs after ep is no longer dereferenced on
each branch.&lt;/p&gt;
&lt;p&gt;Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image
(long filename with same-hash collisions forcing the TYPE_EXTEND path).
With a debug-only invalidate_bdev() inserted between brelse(bh) and
the ep read to make the stale-deref window deterministic, the
unpatched kernel faults:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0
  BUG: unable to handle page fault for address: ffff88801a5fa0c2
  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0&lt;/p&gt;
&lt;p&gt;With this patch applied, the same instrumented harness completes
clean…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-63808</guid>
    </item>
    <item>
      <title>GHSA-rp7p-3v5m-f8gg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rp7p-3v5m-f8gg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;exfat: fix potential use-after-free in exfat_find_dir_entry()&lt;/p&gt;
&lt;p&gt;In exfat_find_dir_entry(), the buffer_head obtained from
exfat_get_dentry() is released with brelse(bh) before the fall-through
TYPE_EXTEND branch reads the directory entry through ep (which points
into bh-&amp;gt;b_data):&lt;/p&gt;
&lt;p&gt;brelse(bh);
	if (entry_type == TYPE_EXTEND) {
		...
		len = exfat_extract_uni_name(ep, entry_uniname);
		...
	}&lt;/p&gt;
&lt;p&gt;After brelse() drops our reference, nothing guarantees that the
underlying page backing bh-&amp;gt;b_data remains valid for the subsequent
exfat_extract_uni_name() read. This is the same pattern fixed in
commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in
exfat_load_upcase_table()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Move brelse(bh) so it runs after ep is no longer dereferenced on
each branch.&lt;/p&gt;
&lt;p&gt;Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image
(long filename with same-hash collisions forcing the TYPE_EXTEND path).
With a debug-only invalidate_bdev() inserted between brelse(bh) and
the ep read to make the stale-deref window deterministic, the
unpatched kernel faults:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0
  BUG: unable to handle page fault for address: ffff88801a5fa0c2
  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0&lt;/p&gt;
&lt;p&gt;With this patch applied, the same instrumented harness completes
clean…&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;exfat: fix potential use-after-free in exfat_find_dir_entry()&lt;/p&gt;
&lt;p&gt;In exfat_find_dir_entry(), the buffer_head obtained from
exfat_get_dentry() is released with brelse(bh) before the fall-through
TYPE_EXTEND branch reads the directory entry through ep (which points
into bh-&amp;gt;b_data):&lt;/p&gt;
&lt;p&gt;brelse(bh);
	if (entry_type == TYPE_EXTEND) {
		...
		len = exfat_extract_uni_name(ep, entry_uniname);
		...
	}&lt;/p&gt;
&lt;p&gt;After brelse() drops our reference, nothing guarantees that the
underlying page backing bh-&amp;gt;b_data remains valid for the subsequent
exfat_extract_uni_name() read. This is the same pattern fixed in
commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in
exfat_load_upcase_table()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Move brelse(bh) so it runs after ep is no longer dereferenced on
each branch.&lt;/p&gt;
&lt;p&gt;Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y
+ CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image
(long filename with same-hash collisions forcing the TYPE_EXTEND path).
With a debug-only invalidate_bdev() inserted between brelse(bh) and
the ep read to make the stale-deref window deterministic, the
unpatched kernel faults:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0
  BUG: unable to handle page fault for address: ffff88801a5fa0c2
  Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI
  RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0&lt;/p&gt;
&lt;p&gt;With this patch applied, the same instrumented harness completes
clean…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rp7p-3v5m-f8gg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-63808 — exfat: fix potential use-after-free in exfat_find_dir_entry()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-63808</link>
      <description>msrc_CVE-2026-63808</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-63808</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</guid>
    </item>
    <item>
      <title>RLSA-2026:63128 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:63128</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)&lt;/p&gt;
&lt;p&gt;* kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)&lt;/p&gt;
&lt;p&gt;* kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)&lt;/p&gt;
&lt;p&gt;* kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)&lt;/p&gt;
&lt;p&gt;* kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)&lt;/p&gt;
&lt;p&gt;* kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)&lt;/p&gt;
&lt;p&gt;* kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)&lt;/p&gt;
&lt;p&gt;* kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)&lt;/p&gt;
&lt;p&gt;* kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&amp;gt;rt6 pointer (CVE-2026-74581)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:63128</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23477-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:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63808</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63808</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry(), the buffer_head obtained from exfat_get_dentry() is released with brelse(bh) before the fall-through TYPE_EXTEND branch reads the directory entry through ep (which points into bh-&amp;gt;b_data): 	brelse(bh); 	if (entry_type == TYPE_EXTEND) { 		... 		len = exfat_extract_uni_name(ep, entry_uniname); 		... 	} After brelse() drops our reference, nothing guarantees that the underlying page backing bh-&amp;gt;b_data remains valid for the subsequent exfat_extract_uni_name() read. This is the same pattern fixed in commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in exfat_load_upcase_table()&amp;#34;). Move brelse(bh) so it runs after ep is no longer dereferenced on each branch. Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y + CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image (long filename with same-hash collisions forcing the TYPE_EXTEND path). With a debug-only invalidate_bdev() inserted between brelse(bh) and the ep read to make the stale-deref window deterministic, the unpatched kernel faults:   BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0   BUG: unable to handle page fault for address: ffff88801a5fa0c2   Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI   RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0 With this patch applied, the same instrumented harness completes cleanly under…&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: exfat: fix potential use-after-free in exfat_find_dir_entry() In exfat_find_dir_entry(), the buffer_head obtained from exfat_get_dentry() is released with brelse(bh) before the fall-through TYPE_EXTEND branch reads the directory entry through ep (which points into bh-&amp;gt;b_data): 	brelse(bh); 	if (entry_type == TYPE_EXTEND) { 		... 		len = exfat_extract_uni_name(ep, entry_uniname); 		... 	} After brelse() drops our reference, nothing guarantees that the underlying page backing bh-&amp;gt;b_data remains valid for the subsequent exfat_extract_uni_name() read. This is the same pattern fixed in commit fc961522ddbd (&amp;#34;exfat: Fix potential use after free in exfat_load_upcase_table()&amp;#34;). Move brelse(bh) so it runs after ep is no longer dereferenced on each branch. Confirmed on QEMU x86_64 with CONFIG_KASAN=y + CONFIG_DEBUG_PAGEALLOC=y + CONFIG_PAGE_POISONING=y on linux-next, using a crafted exFAT image (long filename with same-hash collisions forcing the TYPE_EXTEND path). With a debug-only invalidate_bdev() inserted between brelse(bh) and the ep read to make the stale-deref window deterministic, the unpatched kernel faults:   BUG: KASAN: use-after-free in exfat_find_dir_entry+0x133b/0x15a0   BUG: unable to handle page fault for address: ffff88801a5fa0c2   Oops: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI   RIP: 0010:exfat_find_dir_entry+0x1188/0x15a0 With this patch applied, the same instrumented harness completes cleanly under…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63808</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
