<?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 10:02:47 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:20518 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2025:20518</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 64 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
  * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
  * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
  * kernel: vfs: fix race between evice_inodes() and find_inode()&amp;amp;#38;iput() (CVE-2024-47679)
  * kernel: x86/tdx: Fix &amp;#34;in-kernel MMIO&amp;#34; check (CVE-2024-47727)
  * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
  * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
  * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
  * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
  * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
  * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
  * kernel: afs: Fix lock recursion (CVE-2024-53090)
  * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
  * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
  * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
  * kernel:…&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 64 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
  * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
  * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
  * kernel: vfs: fix race between evice_inodes() and find_inode()&amp;amp;#38;iput() (CVE-2024-47679)
  * kernel: x86/tdx: Fix &amp;#34;in-kernel MMIO&amp;#34; check (CVE-2024-47727)
  * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
  * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
  * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
  * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
  * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
  * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
  * kernel: afs: Fix lock recursion (CVE-2024-53090)
  * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
  * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
  * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
  * kernel:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2025:20518</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-21829</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21829</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-21829</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0277 — 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-2025-avi-0277</link>
      <description>certfr-2025-avi-0277</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0277</guid>
    </item>
    <item>
      <title>OESA-2025-1878 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1878</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;amp;apos;changes_pkt_data&amp;amp;apos; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;amp;apos;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix the warning &amp;amp;quot;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;The Call Trace is as below:
&amp;amp;quot;
  &amp;amp;lt;TASK&amp;amp;gt;
  ? show_regs.cold+0x1a/0x1f
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? __warn+0x84/0xd0
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? report_bug+0x105/0x180
  ? han…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: consider that tail calls invalidate packet pointers&lt;/p&gt;
&lt;p&gt;Tail-called programs could execute any of the helpers that invalidate
packet pointers. Hence, conservatively assume that each tail call
invalidates packet pointers.&lt;/p&gt;
&lt;p&gt;Making the change in bpf_helper_changes_pkt_data() automatically makes
use of check_cfg() logic that computes &amp;amp;apos;changes_pkt_data&amp;amp;apos; effect for
global sub-programs, such that the following program could be
rejected:&lt;/p&gt;
&lt;p&gt;int tail_call(struct __sk_buff *sk)
    {
    	bpf_tail_call_static(sk, &amp;amp;amp;jmp_table, 0);
    	return 0;
    }&lt;/p&gt;
&lt;p&gt;SEC(&amp;amp;quot;tc&amp;amp;quot;)
    int not_safe(struct __sk_buff *sk)
    {
    	int *p = (void *)(long)sk-&amp;amp;gt;data;
    	... make p valid ...
    	tail_call(sk);
    	*p = 42; /* this is unsafe */
    	...
    }&lt;/p&gt;
&lt;p&gt;The tc_bpf2bpf.c:subprog_tc() needs change: mark it as a function that
can invalidate packet pointers. Otherwise, it can&amp;amp;apos;t be freplaced with
tailcall_freplace.c:entry_freplace() that does a tail call.(CVE-2024-58237)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/rxe: Fix the warning &amp;amp;quot;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;The Call Trace is as below:
&amp;amp;quot;
  &amp;amp;lt;TASK&amp;amp;gt;
  ? show_regs.cold+0x1a/0x1f
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? __warn+0x84/0xd0
  ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]
  ? report_bug+0x105/0x180
  ? han…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1878</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21829</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21829</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning &amp;#34;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;#34; The Call Trace is as below: &amp;#34;   &amp;lt;TASK&amp;gt;   ? show_regs.cold+0x1a/0x1f   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? __warn+0x84/0xd0   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? report_bug+0x105/0x180   ? handle_bug+0x46/0x80   ? exc_invalid_op+0x19/0x70   ? asm_exc_invalid_op+0x1b/0x20   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? __rxe_cleanup+0x124/0x170 [rdma_rxe]   rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe]   ib_destroy_qp_user+0x118/0x190 [ib_core]   rdma_destroy_qp.cold+0x43/0x5e [rdma_cm]   rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core]   rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server]   process_one_work+0x21d/0x3f0   worker_thread+0x4a/0x3c0   ? process_one_work+0x3f0/0x3f0   kthread+0xf0/0x120   ? kthread_complete_and_exit+0x20/0x20   ret_from_fork+0x22/0x30   &amp;lt;/TASK&amp;gt; &amp;#34; When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly. Compared with other rdma drivers, a bigger timeout is used.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning &amp;#34;__rxe_cleanup+0x12c/0x170 [rdma_rxe]&amp;#34; The Call Trace is as below: &amp;#34;   &amp;lt;TASK&amp;gt;   ? show_regs.cold+0x1a/0x1f   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? __warn+0x84/0xd0   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? report_bug+0x105/0x180   ? handle_bug+0x46/0x80   ? exc_invalid_op+0x19/0x70   ? asm_exc_invalid_op+0x1b/0x20   ? __rxe_cleanup+0x12c/0x170 [rdma_rxe]   ? __rxe_cleanup+0x124/0x170 [rdma_rxe]   rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe]   ib_destroy_qp_user+0x118/0x190 [ib_core]   rdma_destroy_qp.cold+0x43/0x5e [rdma_cm]   rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core]   rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server]   process_one_work+0x21d/0x3f0   worker_thread+0x4a/0x3c0   ? process_one_work+0x3f0/0x3f0   kthread+0xf0/0x120   ? kthread_complete_and_exit+0x20/0x20   ret_from_fork+0x22/0x30   &amp;lt;/TASK&amp;gt; &amp;#34; When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly. Compared with other rdma drivers, a bigger timeout is used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21829</guid>
    </item>
  </channel>
</rss>
