<?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>Sat, 03 Oct 2026 21:11:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-11535</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-11535</link>
      <description>bdu:2024-11535</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-11535</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — 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-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>EUVD-2026-309824</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309824</link>
      <description>EUVD-2026-309824</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309824</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47583</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47583</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: mxl111sf: change mutex_init() location&lt;/p&gt;
&lt;p&gt;Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.&lt;/p&gt;
&lt;p&gt;Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but
dvb_usbv2_init() has this order of calls:&lt;/p&gt;
&lt;p&gt;dvb_usbv2_init()
	  dvb_usbv2_adapter_init()
	    dvb_usbv2_adapter_frontend_init()
	      props-&amp;gt;frontend_attach()&lt;/p&gt;
&lt;p&gt;props-&amp;gt;init()&lt;/p&gt;
&lt;p&gt;Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach()
internally we need to initialize state-&amp;gt;msg_lock before
frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.&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;media: mxl111sf: change mutex_init() location&lt;/p&gt;
&lt;p&gt;Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.&lt;/p&gt;
&lt;p&gt;Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but
dvb_usbv2_init() has this order of calls:&lt;/p&gt;
&lt;p&gt;dvb_usbv2_init()
	  dvb_usbv2_adapter_init()
	    dvb_usbv2_adapter_frontend_init()
	      props-&amp;gt;frontend_attach()&lt;/p&gt;
&lt;p&gt;props-&amp;gt;init()&lt;/p&gt;
&lt;p&gt;Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach()
internally we need to initialize state-&amp;gt;msg_lock before
frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47583</guid>
    </item>
    <item>
      <title>GHSA-hfwg-2mm4-h8c4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hfwg-2mm4-h8c4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;media: mxl111sf: change mutex_init() location&lt;/p&gt;
&lt;p&gt;Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.&lt;/p&gt;
&lt;p&gt;Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but
dvb_usbv2_init() has this order of calls:&lt;/p&gt;
&lt;p&gt;dvb_usbv2_init()
	  dvb_usbv2_adapter_init()
	    dvb_usbv2_adapter_frontend_init()
	      props-&amp;gt;frontend_attach()&lt;/p&gt;
&lt;p&gt;props-&amp;gt;init()&lt;/p&gt;
&lt;p&gt;Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach()
internally we need to initialize state-&amp;gt;msg_lock before
frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.&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;media: mxl111sf: change mutex_init() location&lt;/p&gt;
&lt;p&gt;Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.&lt;/p&gt;
&lt;p&gt;Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but
dvb_usbv2_init() has this order of calls:&lt;/p&gt;
&lt;p&gt;dvb_usbv2_init()
	  dvb_usbv2_adapter_init()
	    dvb_usbv2_adapter_frontend_init()
	      props-&amp;gt;frontend_attach()&lt;/p&gt;
&lt;p&gt;props-&amp;gt;init()&lt;/p&gt;
&lt;p&gt;Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach()
internally we need to initialize state-&amp;gt;msg_lock before
frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hfwg-2mm4-h8c4</guid>
    </item>
    <item>
      <title>OESA-2024-1835 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1835</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: fix various gadgets null ptr deref on 10gbps cabling.&#13;
&#13;
This avoids a null pointer dereference in
f_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm}
by simply reusing the 5gbps config for 10gbps.(CVE-2021-47270)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
seg6: fix the iif in the IPv6 socket control block&#13;
&#13;
When an IPv4 packet is received, the ip_rcv_core(...) sets the receiving
interface index into the IPv4 socket control block (v5.16-rc4,
net/ipv4/ip_input.c line 510):&#13;
&#13;
    IPCB(skb)-&amp;amp;gt;iif = skb-&amp;amp;gt;skb_iif;&#13;
&#13;
If that IPv4 packet is meant to be encapsulated in an outer IPv6+SRH
header, the seg6_do_srh_encap(...) performs the required encapsulation.
In this case, the seg6_do_srh_encap function clears the IPv6 socket control
block (v5.16-rc4 net/ipv6/seg6_iptunnel.c line 163):&#13;
&#13;
    memset(IP6CB(skb), 0, sizeof(*IP6CB(skb)));&#13;
&#13;
The memset(...) was introduced in commit ef489749aae5 (&amp;amp;quot;ipv6: sr: clear
IP6CB(skb) on SRH ip4ip6 encapsulation&amp;amp;quot;) a long time ago (2019-01-29).&#13;
&#13;
Since the IPv6 socket control block and the IPv4 socket control block share
the same memory area (skb-&amp;amp;gt;cb), the receiving interface index info is lost
(IP6CB(skb)-&amp;amp;gt;iif is set to zero).&#13;
&#13;
As a side effect, that condition triggers a NULL pointer dereference if
commit 0857d6f8c759 (&amp;amp;quot;ip…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
usb: fix various gadgets null ptr deref on 10gbps cabling.&#13;
&#13;
This avoids a null pointer dereference in
f_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm}
by simply reusing the 5gbps config for 10gbps.(CVE-2021-47270)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
seg6: fix the iif in the IPv6 socket control block&#13;
&#13;
When an IPv4 packet is received, the ip_rcv_core(...) sets the receiving
interface index into the IPv4 socket control block (v5.16-rc4,
net/ipv4/ip_input.c line 510):&#13;
&#13;
    IPCB(skb)-&amp;amp;gt;iif = skb-&amp;amp;gt;skb_iif;&#13;
&#13;
If that IPv4 packet is meant to be encapsulated in an outer IPv6+SRH
header, the seg6_do_srh_encap(...) performs the required encapsulation.
In this case, the seg6_do_srh_encap function clears the IPv6 socket control
block (v5.16-rc4 net/ipv6/seg6_iptunnel.c line 163):&#13;
&#13;
    memset(IP6CB(skb), 0, sizeof(*IP6CB(skb)));&#13;
&#13;
The memset(...) was introduced in commit ef489749aae5 (&amp;amp;quot;ipv6: sr: clear
IP6CB(skb) on SRH ip4ip6 encapsulation&amp;amp;quot;) a long time ago (2019-01-29).&#13;
&#13;
Since the IPv6 socket control block and the IPv4 socket control block share
the same memory area (skb-&amp;amp;gt;cb), the receiving interface index info is lost
(IP6CB(skb)-&amp;amp;gt;iif is set to zero).&#13;
&#13;
As a side effect, that condition triggers a NULL pointer dereference if
commit 0857d6f8c759 (&amp;amp;quot;ip…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1835</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2362-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2362-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-2024:2362-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47583</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47583</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4 and 102 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location. Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but dvb_usbv2_init() has this order of calls: 	dvb_usbv2_init() 	  dvb_usbv2_adapter_init() 	    dvb_usbv2_adapter_frontend_init() 	      props-&amp;gt;frontend_attach() 	  props-&amp;gt;init() Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach() internally we need to initialize state-&amp;gt;msg_lock before frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.&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: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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4 and 102 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location. Previous mutex_init(&amp;amp;state-&amp;gt;msg_lock) call was in -&amp;gt;init() function, but dvb_usbv2_init() has this order of calls: 	dvb_usbv2_init() 	  dvb_usbv2_adapter_init() 	    dvb_usbv2_adapter_frontend_init() 	      props-&amp;gt;frontend_attach() 	  props-&amp;gt;init() Since mxl111sf_* devices call mxl111sf_ctrl_msg() in -&amp;gt;frontend_attach() internally we need to initialize state-&amp;gt;msg_lock before frontend_attach(). To achieve it, -&amp;gt;probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47583</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1418 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</guid>
    </item>
  </channel>
</rss>
