<?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 13:21:24 +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>bdu:2026-13980</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13980</link>
      <description>bdu:2026-13980</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13980</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-53073</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53073</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-53073</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — 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-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>EUVD-2026-329964</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329964</link>
      <description>EUVD-2026-329964</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329964</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53073</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53073</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error&lt;/p&gt;
&lt;p&gt;When hci_register_dev() fails in hci_uart_register_dev()
HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu)
and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach
the protocol-specific recv handler in hci_uart_tty_receive() after
resources are freed.&lt;/p&gt;
&lt;p&gt;Clear HCI_UART_PROTO_INIT with a write lock before calling
hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures
all active readers have completed and no new reader can enter the
protocol recv path before resources are freed.&lt;/p&gt;
&lt;p&gt;This allows the protocol-specific recv functions to remove the
&amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference
if hci_register_dev() fails.&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;Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error&lt;/p&gt;
&lt;p&gt;When hci_register_dev() fails in hci_uart_register_dev()
HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu)
and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach
the protocol-specific recv handler in hci_uart_tty_receive() after
resources are freed.&lt;/p&gt;
&lt;p&gt;Clear HCI_UART_PROTO_INIT with a write lock before calling
hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures
all active readers have completed and no new reader can enter the
protocol recv path before resources are freed.&lt;/p&gt;
&lt;p&gt;This allows the protocol-specific recv functions to remove the
&amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference
if hci_register_dev() fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53073</guid>
    </item>
    <item>
      <title>GHSA-wq7c-9cj9-76jg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wq7c-9cj9-76jg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error&lt;/p&gt;
&lt;p&gt;When hci_register_dev() fails in hci_uart_register_dev()
HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu)
and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach
the protocol-specific recv handler in hci_uart_tty_receive() after
resources are freed.&lt;/p&gt;
&lt;p&gt;Clear HCI_UART_PROTO_INIT with a write lock before calling
hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures
all active readers have completed and no new reader can enter the
protocol recv path before resources are freed.&lt;/p&gt;
&lt;p&gt;This allows the protocol-specific recv functions to remove the
&amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference
if hci_register_dev() fails.&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;Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error&lt;/p&gt;
&lt;p&gt;When hci_register_dev() fails in hci_uart_register_dev()
HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu)
and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach
the protocol-specific recv handler in hci_uart_tty_receive() after
resources are freed.&lt;/p&gt;
&lt;p&gt;Clear HCI_UART_PROTO_INIT with a write lock before calling
hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures
all active readers have completed and no new reader can enter the
protocol recv path before resources are freed.&lt;/p&gt;
&lt;p&gt;This allows the protocol-specific recv functions to remove the
&amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference
if hci_register_dev() fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wq7c-9cj9-76jg</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53073 — Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53073</link>
      <description>msrc_CVE-2026-53073</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53073</guid>
    </item>
    <item>
      <title>OESA-2026-3529 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3529</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: core: Fix thermal zone governor cleanup issues&lt;/p&gt;
&lt;p&gt;If thermal_zone_device_register_with_trips() fails after adding
a thermal governor to the thermal zone being registered, the
governor is not removed from it as appropriate which may lead to
a memory leak.&lt;/p&gt;
&lt;p&gt;In turn, thermal_zone_device_unregister() calls thermal_set_governor()
without acquiring the thermal zone lock beforehand which may race with
a governor update via sysfs and may lead to a use-after-free in that
case.&lt;/p&gt;
&lt;p&gt;Address these issues by adding two thermal_set_governor() calls, one to
thermal_release() to remove the governor from the given thermal zone,
and one to the thermal zone registration error path to cover failures
preceding the thermal zone device registration.(CVE-2026-46021)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: authencesn - reject short ahash digests during instance creation&lt;/p&gt;
&lt;p&gt;authencesn requires either a zero authsize or an authsize of at least
4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of
high-order sequence number data at the end of the authenticated data.&lt;/p&gt;
&lt;p&gt;While crypto_authenc_esn_setauthsize() already rejects explicit
non-zero authsizes in the range 1..3, crypto_authenc_esn_create()
still copied auth-&amp;amp;gt;digestsize into inst-&amp;amp;gt;alg.maxauthsize without
validating it.  The AEAD core then initializ…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: core: Fix thermal zone governor cleanup issues&lt;/p&gt;
&lt;p&gt;If thermal_zone_device_register_with_trips() fails after adding
a thermal governor to the thermal zone being registered, the
governor is not removed from it as appropriate which may lead to
a memory leak.&lt;/p&gt;
&lt;p&gt;In turn, thermal_zone_device_unregister() calls thermal_set_governor()
without acquiring the thermal zone lock beforehand which may race with
a governor update via sysfs and may lead to a use-after-free in that
case.&lt;/p&gt;
&lt;p&gt;Address these issues by adding two thermal_set_governor() calls, one to
thermal_release() to remove the governor from the given thermal zone,
and one to the thermal zone registration error path to cover failures
preceding the thermal zone device registration.(CVE-2026-46021)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: authencesn - reject short ahash digests during instance creation&lt;/p&gt;
&lt;p&gt;authencesn requires either a zero authsize or an authsize of at least
4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of
high-order sequence number data at the end of the authenticated data.&lt;/p&gt;
&lt;p&gt;While crypto_authenc_esn_setauthsize() already rejects explicit
non-zero authsizes in the range 1..3, crypto_authenc_esn_create()
still copied auth-&amp;amp;gt;digestsize into inst-&amp;amp;gt;alg.maxauthsize without
validating it.  The AEAD core then initializ…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3529</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21555-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21555-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:21555-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:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53073</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53073</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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu) and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed. This allows the protocol-specific recv functions to remove the &amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference if hci_register_dev() fails.&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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu-&amp;gt;proto-&amp;gt;close(hu) and setting hu-&amp;gt;hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu-&amp;gt;proto-&amp;gt;close() and setting hu-&amp;gt;hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed. This allows the protocol-specific recv functions to remove the &amp;#34;HCI_UART_REGISTERED&amp;#34; guard without risking a null pointer dereference if hci_register_dev() fails.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53073</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>
