<?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 05:29:57 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:16880 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2025:16880</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 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;* kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)
  * kernel: smb: client: fix use-after-free in cifs_oplock_break (CVE-2025-38527)
  * kernel: sctp: linearize cloned gso packets in sctp_rcv (CVE-2025-38718)
  * kernel: tls: fix handling of zero-length records on the rx_list (CVE-2025-39682)
  * kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure (CVE-2025-39698)&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;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 66 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;* kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)
  * kernel: smb: client: fix use-after-free in cifs_oplock_break (CVE-2025-38527)
  * kernel: sctp: linearize cloned gso packets in sctp_rcv (CVE-2025-38718)
  * kernel: tls: fix handling of zero-length records on the rx_list (CVE-2025-39682)
  * kernel: io_uring/futex: ensure io_futex_wait() cleans up properly on failure (CVE-2025-39698)&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;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2025:16880</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38718</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38718</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-2025-38718</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0842 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0842</link>
      <description>certfr-2025-avi-0842</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0842</guid>
    </item>
    <item>
      <title>OESA-2025-2695 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2695</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error&lt;/p&gt;
&lt;p&gt;After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.&lt;/p&gt;
&lt;p&gt;However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:&lt;/p&gt;
&lt;p&gt;remove_proc_entry: removing non-empty directory &amp;amp;apos;irq/30&amp;amp;apos;, leaking at least &amp;amp;apos;pci-endpoint-test.0&amp;amp;apos;
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c&lt;/p&gt;
&lt;p&gt;To solve this issue, set the number of remaining IRQs to test-&amp;amp;gt;num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().&lt;/p&gt;
&lt;p&gt;[kwilczynski: commit log](CVE-2025-23140)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amdgpu: csa unmap use uninterruptible lock&lt;/p&gt;
&lt;p&gt;After process exit to unmap csa and free GPU vm, if signal is accepted
and then waiting to take vm lock is interrupted and return, it causes
memory leaking and below warning backtrace.&lt;/p&gt;
&lt;p&gt;Change to use uninterruptible wait lock fix the issue.&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 69 PID: 167800 at amd/amdgpu/amdgpu_kms.c:1525
 amdgpu_driver_postclose_kms+0x294/0x2a0 [amdgpu]
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  drm_file_free.part.0+0x1da/0x230 [drm]
  drm_clo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2695</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38718</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38718</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 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: linearize cloned gso packets in sctp_rcv A cloned head skb still shares these frag skbs in fraglist with the original head skb. It&amp;#39;s not safe to access these frag skbs. syzbot reported two use-of-uninitialized-memory bugs caused by this:   BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211    sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211    sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998    sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88    sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331    sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122    __release_sock+0x1da/0x330 net/core/sock.c:3106    release_sock+0x6b/0x250 net/core/sock.c:3660    sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360    sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885    sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031    inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851    sock_sendmsg_nosec net/socket.c:718 [inline] and   BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987    sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987    sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88    sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331    sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148    __release_sock+0x1d3/0x330 net/core/sock.c:3213    release_sock+0x6b/0x270 net/core/sock.c:3767    sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367…&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 208 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sctp: linearize cloned gso packets in sctp_rcv A cloned head skb still shares these frag skbs in fraglist with the original head skb. It&amp;#39;s not safe to access these frag skbs. syzbot reported two use-of-uninitialized-memory bugs caused by this:   BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211    sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211    sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998    sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88    sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331    sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122    __release_sock+0x1da/0x330 net/core/sock.c:3106    release_sock+0x6b/0x250 net/core/sock.c:3660    sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360    sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885    sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031    inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851    sock_sendmsg_nosec net/socket.c:718 [inline] and   BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987    sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987    sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88    sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331    sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148    __release_sock+0x1d3/0x330 net/core/sock.c:3213    release_sock+0x6b/0x270 net/core/sock.c:3767    sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38718</guid>
    </item>
  </channel>
</rss>
