<?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 01:45:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2023-53577</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2023-53577</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: 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:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2023-53577</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1009 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-1009</link>
      <description>certfr-2025-avi-1009</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1009</guid>
    </item>
    <item>
      <title>OESA-2026-1504 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-1504</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;bpf, cpumap: Make sure kthread is running before map update returns&lt;/p&gt;
&lt;p&gt;The following warning was reported when running stress-mode enabled
xdp_redirect_cpu with some RT threads:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135
  CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
  Workqueue: events cpu_map_kthread_stop
  RIP: 0010:put_cpu_map_entry+0xda/0x220
  ......
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   ? show_regs+0x65/0x70
   ? __warn+0xa5/0x240
   ......
   ? put_cpu_map_entry+0xda/0x220
   cpu_map_kthread_stop+0x41/0x60
   process_one_work+0x6b0/0xb80
   worker_thread+0x96/0x720
   kthread+0x1a5/0x1f0
   ret_from_fork+0x3a/0x70
   ret_from_fork_asm+0x1b/0x30
   &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The root cause is the same as commit 436901649731 (&amp;amp;quot;bpf: cpumap: Fix memory
leak in cpu_map_update_elem&amp;amp;quot;). The kthread is stopped prematurely by
kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn&amp;amp;apos;t call
cpu_map_kthread_run() at all but XDP program has already queued some
frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks
the ptr_ring, it will find it was not emptied and report a warning.&lt;/p&gt;
&lt;p&gt;An alternative fix is to use __cpu_map_ring_cleanup() to drop these
pending frames or skbs when kthread_stop() returns -EINTR,…&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;bpf, cpumap: Make sure kthread is running before map update returns&lt;/p&gt;
&lt;p&gt;The following warning was reported when running stress-mode enabled
xdp_redirect_cpu with some RT threads:&lt;/p&gt;
&lt;p&gt;------------[ cut here ]------------
  WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135
  CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
  Workqueue: events cpu_map_kthread_stop
  RIP: 0010:put_cpu_map_entry+0xda/0x220
  ......
  Call Trace:
   &amp;amp;lt;TASK&amp;amp;gt;
   ? show_regs+0x65/0x70
   ? __warn+0xa5/0x240
   ......
   ? put_cpu_map_entry+0xda/0x220
   cpu_map_kthread_stop+0x41/0x60
   process_one_work+0x6b0/0xb80
   worker_thread+0x96/0x720
   kthread+0x1a5/0x1f0
   ret_from_fork+0x3a/0x70
   ret_from_fork_asm+0x1b/0x30
   &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The root cause is the same as commit 436901649731 (&amp;amp;quot;bpf: cpumap: Fix memory
leak in cpu_map_update_elem&amp;amp;quot;). The kthread is stopped prematurely by
kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn&amp;amp;apos;t call
cpu_map_kthread_run() at all but XDP program has already queued some
frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks
the ptr_ring, it will find it was not emptied and report a warning.&lt;/p&gt;
&lt;p&gt;An alternative fix is to use __cpu_map_ring_cleanup() to drop these
pending frames or skbs when kthread_stop() returns -EINTR,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-1504</guid>
    </item>
    <item>
      <title>RXSA-2024:3138 — Moderate: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rxsa-2024:3138</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debug-modules and 14 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debug-modules and 14 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;
&lt;p&gt;Additional Changes:&lt;/p&gt;
&lt;p&gt;For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rxsa-2024:3138</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53577</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53577</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:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Make sure kthread is running before map update returns The following warning was reported when running stress-mode enabled xdp_redirect_cpu with some RT threads:   ------------[ cut here ]------------   WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135   CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)   Workqueue: events cpu_map_kthread_stop   RIP: 0010:put_cpu_map_entry+0xda/0x220   ......   Call Trace:    &amp;lt;TASK&amp;gt;    ? show_regs+0x65/0x70    ? __warn+0xa5/0x240    ......    ? put_cpu_map_entry+0xda/0x220    cpu_map_kthread_stop+0x41/0x60    process_one_work+0x6b0/0xb80    worker_thread+0x96/0x720    kthread+0x1a5/0x1f0    ret_from_fork+0x3a/0x70    ret_from_fork_asm+0x1b/0x30    &amp;lt;/TASK&amp;gt; The root cause is the same as commit 436901649731 (&amp;#34;bpf: cpumap: Fix memory leak in cpu_map_update_elem&amp;#34;). The kthread is stopped prematurely by kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn&amp;#39;t call cpu_map_kthread_run() at all but XDP program has already queued some frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks the ptr_ring, it will find it was not emptied and report a warning. An alternative fix is to use __cpu_map_ring_cleanup() to drop these pending frames or skbs when kthread_stop() returns -EINTR, but it may confuse the user, because these frames or skbs have been handled correctly by XDP program. So i…&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:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Make sure kthread is running before map update returns The following warning was reported when running stress-mode enabled xdp_redirect_cpu with some RT threads:   ------------[ cut here ]------------   WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135   CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)   Workqueue: events cpu_map_kthread_stop   RIP: 0010:put_cpu_map_entry+0xda/0x220   ......   Call Trace:    &amp;lt;TASK&amp;gt;    ? show_regs+0x65/0x70    ? __warn+0xa5/0x240    ......    ? put_cpu_map_entry+0xda/0x220    cpu_map_kthread_stop+0x41/0x60    process_one_work+0x6b0/0xb80    worker_thread+0x96/0x720    kthread+0x1a5/0x1f0    ret_from_fork+0x3a/0x70    ret_from_fork_asm+0x1b/0x30    &amp;lt;/TASK&amp;gt; The root cause is the same as commit 436901649731 (&amp;#34;bpf: cpumap: Fix memory leak in cpu_map_update_elem&amp;#34;). The kthread is stopped prematurely by kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn&amp;#39;t call cpu_map_kthread_run() at all but XDP program has already queued some frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks the ptr_ring, it will find it was not emptied and report a warning. An alternative fix is to use __cpu_map_ring_cleanup() to drop these pending frames or skbs when kthread_stop() returns -EINTR, but it may confuse the user, because these frames or skbs have been handled correctly by XDP program. So i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53577</guid>
    </item>
  </channel>
</rss>
