<?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 02:24:11 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-50121</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-50121</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-50121</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1102 — 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://127.0.0.1:10001/vuln/certfr-2024-avi-1102</link>
      <description>certfr-2024-avi-1102</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-1102</guid>
    </item>
    <item>
      <title>OESA-2024-2590 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2590</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
af_unix: Update unix_sk(sk)-&amp;amp;gt;oob_skb under sk_receive_queue lock.&#13;
&#13;
Billy Jheng Bing-Jhong reported a race between __unix_gc() and
queue_oob().&#13;
&#13;
__unix_gc() tries to garbage-collect close()d inflight sockets,
and then if the socket has MSG_OOB in unix_sk(sk)-&amp;amp;gt;oob_skb, GC
will drop the reference and set NULL to it locklessly.&#13;
&#13;
However, the peer socket still can send MSG_OOB message and
queue_oob() can update unix_sk(sk)-&amp;amp;gt;oob_skb concurrently, leading
NULL pointer dereference. [0]&#13;
&#13;
To fix the issue, let&amp;amp;apos;s update unix_sk(sk)-&amp;amp;gt;oob_skb under the
sk_receive_queue&amp;amp;apos;s lock and take it everywhere we touch oob_skb.&#13;
&#13;
Note that we defer kfree_skb() in manage_oob() to silence lockdep
false-positive (See [1]).&#13;
&#13;
[0]:
BUG: kernel NULL pointer dereference, address: 0000000000000008
 PF: supervisor write access in kernel mode
 PF: error_code(0x0002) - not-present page
PGD 8000000009f5e067 P4D 8000000009f5e067 PUD 9f5d067 PMD 0
Oops: 0002 [#1] PREEMPT SMP PTI
CPU: 3 PID: 50 Comm: kworker/3:1 Not tainted 6.9.0-rc5-00191-gd091e579b864 #110
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
Workqueue: events delayed_fput
RIP: 0010:skb_dequeue (./include/linux/skbuff.h:2386 ./include/linux/skbuff.h:2402 net/core/skbuff.c:3847)
Code: 39 e3 74 3e 8b 43 10 48 8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;
af_unix: Update unix_sk(sk)-&amp;amp;gt;oob_skb under sk_receive_queue lock.&#13;
&#13;
Billy Jheng Bing-Jhong reported a race between __unix_gc() and
queue_oob().&#13;
&#13;
__unix_gc() tries to garbage-collect close()d inflight sockets,
and then if the socket has MSG_OOB in unix_sk(sk)-&amp;amp;gt;oob_skb, GC
will drop the reference and set NULL to it locklessly.&#13;
&#13;
However, the peer socket still can send MSG_OOB message and
queue_oob() can update unix_sk(sk)-&amp;amp;gt;oob_skb concurrently, leading
NULL pointer dereference. [0]&#13;
&#13;
To fix the issue, let&amp;amp;apos;s update unix_sk(sk)-&amp;amp;gt;oob_skb under the
sk_receive_queue&amp;amp;apos;s lock and take it everywhere we touch oob_skb.&#13;
&#13;
Note that we defer kfree_skb() in manage_oob() to silence lockdep
false-positive (See [1]).&#13;
&#13;
[0]:
BUG: kernel NULL pointer dereference, address: 0000000000000008
 PF: supervisor write access in kernel mode
 PF: error_code(0x0002) - not-present page
PGD 8000000009f5e067 P4D 8000000009f5e067 PUD 9f5d067 PMD 0
Oops: 0002 [#1] PREEMPT SMP PTI
CPU: 3 PID: 50 Comm: kworker/3:1 Not tainted 6.9.0-rc5-00191-gd091e579b864 #110
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
Workqueue: events delayed_fput
RIP: 0010:skb_dequeue (./include/linux/skbuff.h:2386 ./include/linux/skbuff.h:2402 net/core/skbuff.c:3847)
Code: 39 e3 74 3e 8b 43 10 48 8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2590</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-50121</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50121</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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net In the normal case, when we excute `echo 0 &amp;gt; /proc/fs/nfsd/threads`, the function `nfs4_state_destroy_net` in `nfs4_state_shutdown_net` will release all resources related to the hashed `nfs4_client`. If the `nfsd_client_shrinker` is running concurrently, the `expire_client` function will first unhash this client and then destroy it. This can lead to the following warning. Additionally, numerous use-after-free errors may occur as well. nfsd_client_shrinker         echo 0 &amp;gt; /proc/fs/nfsd/threads expire_client                nfsd_shutdown_net   unhash_client                ...                                nfs4_state_shutdown_net                                  /* won&amp;#39;t wait shrinker exit */   /*                             cancel_work(&amp;amp;nn-&amp;gt;nfsd_shrinker_work)    * nfsd_file for this          /* won&amp;#39;t destroy unhashed client1 */    * client1 still alive         nfs4_state_destroy_net    */                                nfsd_file_cache_shutdown                                  /* trigger warning */                                  kmem_cache_destroy(nfsd_file_slab)                                  kmem_cache_destroy(nfsd_file_mark_slab)   /* release nfsd_file and mark */   __destroy_client ==================================================================== BUG nfsd_file (Not tainted): Objects remaining in nfsd_file on __kmem_cache_shu…&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 137 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: cancel nfsd_shrinker_work using sync mode in nfs4_state_shutdown_net In the normal case, when we excute `echo 0 &amp;gt; /proc/fs/nfsd/threads`, the function `nfs4_state_destroy_net` in `nfs4_state_shutdown_net` will release all resources related to the hashed `nfs4_client`. If the `nfsd_client_shrinker` is running concurrently, the `expire_client` function will first unhash this client and then destroy it. This can lead to the following warning. Additionally, numerous use-after-free errors may occur as well. nfsd_client_shrinker         echo 0 &amp;gt; /proc/fs/nfsd/threads expire_client                nfsd_shutdown_net   unhash_client                ...                                nfs4_state_shutdown_net                                  /* won&amp;#39;t wait shrinker exit */   /*                             cancel_work(&amp;amp;nn-&amp;gt;nfsd_shrinker_work)    * nfsd_file for this          /* won&amp;#39;t destroy unhashed client1 */    * client1 still alive         nfs4_state_destroy_net    */                                nfsd_file_cache_shutdown                                  /* trigger warning */                                  kmem_cache_destroy(nfsd_file_slab)                                  kmem_cache_destroy(nfsd_file_mark_slab)   /* release nfsd_file and mark */   __destroy_client ==================================================================== BUG nfsd_file (Not tainted): Objects remaining in nfsd_file on __kmem_cache_shu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50121</guid>
    </item>
  </channel>
</rss>
