<?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>Sun, 04 Oct 2026 14:34:01 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02604</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02604</link>
      <description>bdu:2026-02604</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02604</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0252 — 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://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</link>
      <description>certfr-2025-avi-0252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0252</guid>
    </item>
    <item>
      <title>EUVD-2026-310485</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-310485</link>
      <description>EUVD-2026-310485</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-310485</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49326</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49326</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtl818x: Prevent using not initialized queues&lt;/p&gt;
&lt;p&gt;Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.
Ignore the skb priority for those cards, they only have one tx queue. Pierre
Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum:&lt;/p&gt;
&lt;p&gt;https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html&lt;/p&gt;
&lt;p&gt;He also confirmed that this patch fixes the issue. In summary this happened:&lt;/p&gt;
&lt;p&gt;After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a
&amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to
use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in
2.10.&lt;/p&gt;
&lt;p&gt;Since only the rtl8187se part of the driver supports QoS, the priority
of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185
cards.&lt;/p&gt;
&lt;p&gt;rtl8180 is then unconditionally reading out the priority and finally crashes on
drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this
patch:
	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries&lt;/p&gt;
&lt;p&gt;&amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got
initialized.&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;rtl818x: Prevent using not initialized queues&lt;/p&gt;
&lt;p&gt;Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.
Ignore the skb priority for those cards, they only have one tx queue. Pierre
Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum:&lt;/p&gt;
&lt;p&gt;https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html&lt;/p&gt;
&lt;p&gt;He also confirmed that this patch fixes the issue. In summary this happened:&lt;/p&gt;
&lt;p&gt;After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a
&amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to
use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in
2.10.&lt;/p&gt;
&lt;p&gt;Since only the rtl8187se part of the driver supports QoS, the priority
of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185
cards.&lt;/p&gt;
&lt;p&gt;rtl8180 is then unconditionally reading out the priority and finally crashes on
drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this
patch:
	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries&lt;/p&gt;
&lt;p&gt;&amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got
initialized.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49326</guid>
    </item>
    <item>
      <title>GHSA-3v9q-m8x4-6crj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3v9q-m8x4-6crj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rtl818x: Prevent using not initialized queues&lt;/p&gt;
&lt;p&gt;Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.
Ignore the skb priority for those cards, they only have one tx queue. Pierre
Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum:&lt;/p&gt;
&lt;p&gt;https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html&lt;/p&gt;
&lt;p&gt;He also confirmed that this patch fixes the issue. In summary this happened:&lt;/p&gt;
&lt;p&gt;After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a
&amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to
use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in
2.10.&lt;/p&gt;
&lt;p&gt;Since only the rtl8187se part of the driver supports QoS, the priority
of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185
cards.&lt;/p&gt;
&lt;p&gt;rtl8180 is then unconditionally reading out the priority and finally crashes on
drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this
patch:
	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries&lt;/p&gt;
&lt;p&gt;&amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got
initialized.&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;rtl818x: Prevent using not initialized queues&lt;/p&gt;
&lt;p&gt;Using not existing queues can panic the kernel with rtl8180/rtl8185 cards.
Ignore the skb priority for those cards, they only have one tx queue. Pierre
Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum:&lt;/p&gt;
&lt;p&gt;https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html&lt;/p&gt;
&lt;p&gt;He also confirmed that this patch fixes the issue. In summary this happened:&lt;/p&gt;
&lt;p&gt;After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a
&amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to
use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in
2.10.&lt;/p&gt;
&lt;p&gt;Since only the rtl8187se part of the driver supports QoS, the priority
of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185
cards.&lt;/p&gt;
&lt;p&gt;rtl8180 is then unconditionally reading out the priority and finally crashes on
drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this
patch:
	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries&lt;/p&gt;
&lt;p&gt;&amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got
initialized.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3v9q-m8x4-6crj</guid>
    </item>
    <item>
      <title>OESA-2025-1282 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1282</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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ARM: davinci: da850-evm: Avoid NULL pointer dereference&lt;/p&gt;
&lt;p&gt;With newer versions of GCC, there is a panic in da850_evm_config_emac()
when booting multi_v5_defconfig in QEMU under the palmetto-bmc machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 00000020
pgd = (ptrval)
[00000020] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.0 #1
Hardware name: Generic DT based system
PC is at da850_evm_config_emac+0x1c/0x120
LR is at do_one_initcall+0x50/0x1e0&lt;/p&gt;
&lt;p&gt;The emac_pdata pointer in soc_info is NULL because davinci_soc_info only
gets populated on davinci machines but da850_evm_config_emac() is called
on all machines via device_initcall().&lt;/p&gt;
&lt;p&gt;Move the rmii_en assignment below the machine check so that it is only
dereferenced when running on a supported SoC.(CVE-2021-47631)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow&lt;/p&gt;
&lt;p&gt;Coverity complains of a possible buffer overflow. However,
given the &amp;amp;apos;static&amp;amp;apos; scope of nvidia_setup_i2c_bus() it looks
like that can&amp;amp;apos;t happen after examiniing the call sites.&lt;/p&gt;
&lt;p&gt;CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
1. fixed_size_dest: You might overrun the 48-character fixed-size string
  chan-&amp;amp;gt;adapter.name…&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;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ARM: davinci: da850-evm: Avoid NULL pointer dereference&lt;/p&gt;
&lt;p&gt;With newer versions of GCC, there is a panic in da850_evm_config_emac()
when booting multi_v5_defconfig in QEMU under the palmetto-bmc machine:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 00000020
pgd = (ptrval)
[00000020] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 5.15.0 #1
Hardware name: Generic DT based system
PC is at da850_evm_config_emac+0x1c/0x120
LR is at do_one_initcall+0x50/0x1e0&lt;/p&gt;
&lt;p&gt;The emac_pdata pointer in soc_info is NULL because davinci_soc_info only
gets populated on davinci machines but da850_evm_config_emac() is called
on all machines via device_initcall().&lt;/p&gt;
&lt;p&gt;Move the rmii_en assignment below the machine check so that it is only
dereferenced when running on a supported SoC.(CVE-2021-47631)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow&lt;/p&gt;
&lt;p&gt;Coverity complains of a possible buffer overflow. However,
given the &amp;amp;apos;static&amp;amp;apos; scope of nvidia_setup_i2c_bus() it looks
like that can&amp;amp;apos;t happen after examiniing the call sites.&lt;/p&gt;
&lt;p&gt;CID 19036 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
1. fixed_size_dest: You might overrun the 48-character fixed-size string
  chan-&amp;amp;gt;adapter.name…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1282</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01983-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-2025:01983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49326</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49326</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum: https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html He also confirmed that this patch fixes the issue. In summary this happened: After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a &amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in 2.10. Since only the rtl8187se part of the driver supports QoS, the priority of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185 cards. rtl8180 is then unconditionally reading out the priority and finally crashes on drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this patch: 	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries &amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got initialized.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 144 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum: https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html He also confirmed that this patch fixes the issue. In summary this happened: After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a &amp;#34;divide error: 0000&amp;#34; when connecting to an AP. Control port tx now tries to use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in 2.10. Since only the rtl8187se part of the driver supports QoS, the priority of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185 cards. rtl8180 is then unconditionally reading out the priority and finally crashes on drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this patch: 	idx = (ring-&amp;gt;idx + skb_queue_len(&amp;amp;ring-&amp;gt;queue)) % ring-&amp;gt;entries &amp;#34;ring-&amp;gt;entries&amp;#34; is zero for rtl8180/rtl8185 cards, tx_ring[2] never got initialized.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49326</guid>
    </item>
  </channel>
</rss>
