<?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://127.0.0.1:10001</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, 21 Nov 2026 03:18:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-38578</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-38578</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://127.0.0.1:10001/vuln/bell-cve-2024-38578</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0527 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</link>
      <description>certfr-2024-avi-0527</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0527</guid>
    </item>
    <item>
      <title>OESA-2024-1835 — kernel security update</title>
      <link>https://127.0.0.1:10001/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://127.0.0.1:10001/vuln/oesa-2024-1835</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-38578</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38578</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ecryptfs: Fix buffer size for tag 66 packet The &amp;#39;TAG 66 Packet Format&amp;#39; description is missing the cipher code and checksum fields that are packed into the message packet. As a result, the buffer allocated for the packet is 3 bytes too small and write_tag_66_packet() will write up to 3 bytes past the end of the buffer. Fix this by increasing the size of the allocation so the whole packet will always fit in the buffer. This fixes the below kasan slab-out-of-bounds bug:   BUG: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0   Write of size 1 at addr ffff88800afbb2a5 by task touch/181   CPU: 0 PID: 181 Comm: touch Not tainted 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 04/01/2014   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x4c/0x70    print_report+0xc5/0x610    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    ? kasan_complete_mode_report_info+0x44/0x210    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    kasan_report+0xc2/0x110    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    __asan_store1+0x62/0x80    ecryptfs_generate_key_packet_set+0x7d6/0xde0    ? __pfx_ecryptfs_generate_key_packet_set+0x10/0x10    ? __alloc_pages+0x2e2/0x540    ? __pfx_ovl_open+0x10/0x10 [overlay 30837f11141636a8e1793533a02e6e2e885dad1d]    ? dentry_open+0x8f/0xd0    ecryptfs_write_metadata+0x30a/0x550    ? __pfx_ecryptfs_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 185 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ecryptfs: Fix buffer size for tag 66 packet The &amp;#39;TAG 66 Packet Format&amp;#39; description is missing the cipher code and checksum fields that are packed into the message packet. As a result, the buffer allocated for the packet is 3 bytes too small and write_tag_66_packet() will write up to 3 bytes past the end of the buffer. Fix this by increasing the size of the allocation so the whole packet will always fit in the buffer. This fixes the below kasan slab-out-of-bounds bug:   BUG: KASAN: slab-out-of-bounds in ecryptfs_generate_key_packet_set+0x7d6/0xde0   Write of size 1 at addr ffff88800afbb2a5 by task touch/181   CPU: 0 PID: 181 Comm: touch Not tainted 6.6.13-gnu #1 4c9534092be820851bb687b82d1f92a426598dc6   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2/GNU Guix 04/01/2014   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x4c/0x70    print_report+0xc5/0x610    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    ? kasan_complete_mode_report_info+0x44/0x210    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    kasan_report+0xc2/0x110    ? ecryptfs_generate_key_packet_set+0x7d6/0xde0    __asan_store1+0x62/0x80    ecryptfs_generate_key_packet_set+0x7d6/0xde0    ? __pfx_ecryptfs_generate_key_packet_set+0x10/0x10    ? __alloc_pages+0x2e2/0x540    ? __pfx_ovl_open+0x10/0x10 [overlay 30837f11141636a8e1793533a02e6e2e885dad1d]    ? dentry_open+0x8f/0xd0    ecryptfs_write_metadata+0x30a/0x550    ? __pfx_ecryptfs_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-38578</guid>
    </item>
  </channel>
</rss>
