<?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 00:51:07 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:1690 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:1690</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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;* kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)
  * kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem (CVE-2025-38022)
  * kernel: Linux kernel use-after-free in eventpoll (CVE-2025-38349)
  * kernel: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU (CVE-2025-38453)
  * kernel: net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (CVE-2025-38568)
  * kernel: drm/xe: Fix vm_bind_ioctl double free bug (CVE-2025-38731)
  * kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)
  * kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)
  * kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)
  * kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)
  * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)
  * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
  * kernel: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (CVE-2025-40251)
  * kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
  * kernel: Linux kernel: Out-of-bounds write in Bluetooth MGMT can lead to information disclosure and denial of service (CVE-2025-40294)
  * kernel: Linux kernel: Information disclosure a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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;* kernel: Linux kernel: irqchip/gic-v2m use-after-free vulnerability (CVE-2025-37819)
  * kernel: RDMA/core: Fix &amp;#34;KASAN: slab-use-after-free Read in ib_register_device&amp;#34; problem (CVE-2025-38022)
  * kernel: Linux kernel use-after-free in eventpoll (CVE-2025-38349)
  * kernel: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU (CVE-2025-38453)
  * kernel: net/sched: mqprio: fix stack out-of-bounds write in tc entry parsing (CVE-2025-38568)
  * kernel: drm/xe: Fix vm_bind_ioctl double free bug (CVE-2025-38731)
  * kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)
  * kernel: net: use dst_dev_rcu() in sk_setup_caps() (CVE-2025-40170)
  * kernel: ipv6: use RCU in ip6_xmit() (CVE-2025-40135)
  * kernel: ipv6: use RCU in ip6_output() (CVE-2025-40158)
  * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)
  * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)
  * kernel: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (CVE-2025-40251)
  * kernel: Linux kernel: Use-after-free in proc_readdir_de() can lead to privilege escalation or denial of service. (CVE-2025-40271)
  * kernel: Linux kernel: Out-of-bounds write in Bluetooth MGMT can lead to information disclosure and denial of service (CVE-2025-40294)
  * kernel: Linux kernel: Information disclosure a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:1690</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38453</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38453</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-2025-38453</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0723 — 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-2025-avi-0723</link>
      <description>certfr-2025-avi-0723</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0723</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38453</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38453</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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU syzbot reports that defer/local task_work adding via msg_ring can hit a request that has been freed: CPU: 1 UID: 0 PID: 19356 Comm: iou-wrk-19354 Not tainted 6.16.0-rc4-syzkaller-00108-g17bbde2e1716 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120  print_address_description mm/kasan/report.c:408 [inline]  print_report+0xd2/0x2b0 mm/kasan/report.c:521  kasan_report+0x118/0x150 mm/kasan/report.c:634  io_req_local_work_add io_uring/io_uring.c:1184 [inline]  __io_req_task_work_add+0x589/0x950 io_uring/io_uring.c:1252  io_msg_remote_post io_uring/msg_ring.c:103 [inline]  io_msg_data_remote io_uring/msg_ring.c:133 [inline]  __io_msg_ring_data+0x820/0xaa0 io_uring/msg_ring.c:151  io_msg_ring_data io_uring/msg_ring.c:173 [inline]  io_msg_ring+0x134/0xa00 io_uring/msg_ring.c:314  __io_issue_sqe+0x17e/0x4b0 io_uring/io_uring.c:1739  io_issue_sqe+0x165/0xfd0 io_uring/io_uring.c:1762  io_wq_submit_work+0x6e9/0xb90 io_uring/io_uring.c:1874  io_worker_handle_work+0x7cd/0x1180 io_uring/io-wq.c:642  io_wq_worker+0x42f/0xeb0 io_uring/io-wq.c:696  ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245  &amp;lt;/TASK&amp;gt; which is supposed to be safe with how requests are allocated. But msg r…&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 87 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU syzbot reports that defer/local task_work adding via msg_ring can hit a request that has been freed: CPU: 1 UID: 0 PID: 19356 Comm: iou-wrk-19354 Not tainted 6.16.0-rc4-syzkaller-00108-g17bbde2e1716 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace:  &amp;lt;TASK&amp;gt;  dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120  print_address_description mm/kasan/report.c:408 [inline]  print_report+0xd2/0x2b0 mm/kasan/report.c:521  kasan_report+0x118/0x150 mm/kasan/report.c:634  io_req_local_work_add io_uring/io_uring.c:1184 [inline]  __io_req_task_work_add+0x589/0x950 io_uring/io_uring.c:1252  io_msg_remote_post io_uring/msg_ring.c:103 [inline]  io_msg_data_remote io_uring/msg_ring.c:133 [inline]  __io_msg_ring_data+0x820/0xaa0 io_uring/msg_ring.c:151  io_msg_ring_data io_uring/msg_ring.c:173 [inline]  io_msg_ring+0x134/0xa00 io_uring/msg_ring.c:314  __io_issue_sqe+0x17e/0x4b0 io_uring/io_uring.c:1739  io_issue_sqe+0x165/0xfd0 io_uring/io_uring.c:1762  io_wq_submit_work+0x6e9/0xb90 io_uring/io_uring.c:1874  io_worker_handle_work+0x7cd/0x1180 io_uring/io-wq.c:642  io_wq_worker+0x42f/0xeb0 io_uring/io-wq.c:696  ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245  &amp;lt;/TASK&amp;gt; which is supposed to be safe with how requests are allocated. But msg r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38453</guid>
    </item>
  </channel>
</rss>
