<?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 13:43:13 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-10574</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-10574</link>
      <description>bdu:2024-10574</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-10574</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-344505</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344505</link>
      <description>EUVD-2026-344505</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344505</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47515</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47515</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;seg6: fix the iif in the IPv6 socket control block&lt;/p&gt;
&lt;p&gt;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):&lt;/p&gt;
&lt;p&gt;IPCB(skb)-&amp;gt;iif = skb-&amp;gt;skb_iif;&lt;/p&gt;
&lt;p&gt;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):&lt;/p&gt;
&lt;p&gt;memset(IP6CB(skb), 0, sizeof(*IP6CB(skb)));&lt;/p&gt;
&lt;p&gt;The memset(...) was introduced in commit ef489749aae5 (&amp;#34;ipv6: sr: clear
IP6CB(skb) on SRH ip4ip6 encapsulation&amp;#34;) a long time ago (2019-01-29).&lt;/p&gt;
&lt;p&gt;Since the IPv6 socket control block and the IPv4 socket control block share
the same memory area (skb-&amp;gt;cb), the receiving interface index info is lost
(IP6CB(skb)-&amp;gt;iif is set to zero).&lt;/p&gt;
&lt;p&gt;As a side effect, that condition triggers a NULL pointer dereference if
commit 0857d6f8c759 (&amp;#34;ipv6: When forwarding count rx stats on the orig
netdev&amp;#34;) is applied.&lt;/p&gt;
&lt;p&gt;To fix that issue, we set the IP6CB(skb)-&amp;gt;iif with the index of the
receiving interface once again.&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;seg6: fix the iif in the IPv6 socket control block&lt;/p&gt;
&lt;p&gt;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):&lt;/p&gt;
&lt;p&gt;IPCB(skb)-&amp;gt;iif = skb-&amp;gt;skb_iif;&lt;/p&gt;
&lt;p&gt;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):&lt;/p&gt;
&lt;p&gt;memset(IP6CB(skb), 0, sizeof(*IP6CB(skb)));&lt;/p&gt;
&lt;p&gt;The memset(...) was introduced in commit ef489749aae5 (&amp;#34;ipv6: sr: clear
IP6CB(skb) on SRH ip4ip6 encapsulation&amp;#34;) a long time ago (2019-01-29).&lt;/p&gt;
&lt;p&gt;Since the IPv6 socket control block and the IPv4 socket control block share
the same memory area (skb-&amp;gt;cb), the receiving interface index info is lost
(IP6CB(skb)-&amp;gt;iif is set to zero).&lt;/p&gt;
&lt;p&gt;As a side effect, that condition triggers a NULL pointer dereference if
commit 0857d6f8c759 (&amp;#34;ipv6: When forwarding count rx stats on the orig
netdev&amp;#34;) is applied.&lt;/p&gt;
&lt;p&gt;To fix that issue, we set the IP6CB(skb)-&amp;gt;iif with the index of the
receiving interface once again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47515</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>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&amp;#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2372-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2372-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:2372-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47515</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47515</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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: seg6: fix the iif in the IPv6 socket control block 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):     IPCB(skb)-&amp;gt;iif = skb-&amp;gt;skb_iif; 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):     memset(IP6CB(skb), 0, sizeof(*IP6CB(skb))); The memset(...) was introduced in commit ef489749aae5 (&amp;#34;ipv6: sr: clear IP6CB(skb) on SRH ip4ip6 encapsulation&amp;#34;) a long time ago (2019-01-29). Since the IPv6 socket control block and the IPv4 socket control block share the same memory area (skb-&amp;gt;cb), the receiving interface index info is lost (IP6CB(skb)-&amp;gt;iif is set to zero). As a side effect, that condition triggers a NULL pointer dereference if commit 0857d6f8c759 (&amp;#34;ipv6: When forwarding count rx stats on the orig netdev&amp;#34;) is applied. To fix that issue, we set the IP6CB(skb)-&amp;gt;iif with the index of the receiving interface once again.&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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 99 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: seg6: fix the iif in the IPv6 socket control block 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):     IPCB(skb)-&amp;gt;iif = skb-&amp;gt;skb_iif; 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):     memset(IP6CB(skb), 0, sizeof(*IP6CB(skb))); The memset(...) was introduced in commit ef489749aae5 (&amp;#34;ipv6: sr: clear IP6CB(skb) on SRH ip4ip6 encapsulation&amp;#34;) a long time ago (2019-01-29). Since the IPv6 socket control block and the IPv4 socket control block share the same memory area (skb-&amp;gt;cb), the receiving interface index info is lost (IP6CB(skb)-&amp;gt;iif is set to zero). As a side effect, that condition triggers a NULL pointer dereference if commit 0857d6f8c759 (&amp;#34;ipv6: When forwarding count rx stats on the orig netdev&amp;#34;) is applied. To fix that issue, we set the IP6CB(skb)-&amp;gt;iif with the index of the receiving interface once again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47515</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1235 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1235</guid>
    </item>
  </channel>
</rss>
