<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 18:28:45 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-0895 — 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://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</link>
      <description>CERTFR-2025-AVI-0895</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</guid>
    </item>
    <item>
      <title>bdu:2026-05956</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-05956</link>
      <description>bdu:2026-05956</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-05956</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50271</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2022-50271</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2022-50271</guid>
    </item>
    <item>
      <title>GHSA-7qgr-rfmm-pgc2</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-7qgr-rfmm-pgc2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-7qgr-rfmm-pgc2</guid>
    </item>
    <item>
      <title>RHSA-2023:2458 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:2458</link>
      <description>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;hw: cpu: AMD CPUs may transiently execute beyond unconditional direct branch kernel: ext4: kernel bug in ext4_write_inline_data_end() kernel: malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs kernel: mlxsw: thermal: Fix out-of-bounds memory accesses kernel: mlxsw: spectrum: Protect driver from buggy firmware kernel: net: stmmac: fix tc flower deletion for VLAN priority Rx steering kernel: can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path kernel: possible race condition in drivers/tty/tty_buffers.c kernel: KVM: NULL pointer dereference in kvm_mmu_invpcid_gva kernel: use-after-free in free_pipe_info() could lead to privilege escalation kernel: KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks kernel: netfilter: nf_conntrack_irc message handling issue kernel: race condition in xfrm_probe_algs can lead to OOB read/write kernel: out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c kernel: race condition in hugetlb_no_page() in mm/hugetlb.c kernel: memory leak in ipv6_renew_options() kernel: data races around icsk-&amp;gt;icsk_af_ops in do_ipv6_setsockopt kernel: data races around sk-&amp;gt;sk_prot kernel: memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c kernel: denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry kernel: use-after-free after failed devlink relo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:2458</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03613-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:03613-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2025:03613-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50271</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50271</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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 147 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: Use kvmalloc/kvfree for larger packets. When copying a large file over sftp over vsock, data size is usually 32kB, and kmalloc seems to fail to try to allocate 32 32kB regions.  vhost-5837: page allocation failure: order:4, mode:0x24040c0  Call Trace:   [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb   [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138   [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8   [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d   [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19   [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb   [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7   [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d   [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]   [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]   [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105   [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]   [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3   [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80   [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3 Work around by doing kvmalloc instead.&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:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 147 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vhost/vsock: Use kvmalloc/kvfree for larger packets. When copying a large file over sftp over vsock, data size is usually 32kB, and kmalloc seems to fail to try to allocate 32 32kB regions.  vhost-5837: page allocation failure: order:4, mode:0x24040c0  Call Trace:   [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb   [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138   [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8   [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d   [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19   [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb   [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7   [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d   [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]   [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]   [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105   [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]   [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3   [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80   [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3 Work around by doing kvmalloc instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-50271</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2053</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2053</guid>
    </item>
  </channel>
</rss>
