<?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 03:11:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21776</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21776</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-21776</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-1285 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1285</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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client()&lt;/p&gt;
&lt;p&gt;name is char[64] where the size of clnt-&amp;amp;gt;cl_program-&amp;amp;gt;name remains
unknown. Invoking strcat() directly will also lead to potential buffer
overflow. Change them to strscpy() and strncat() to fix potential
issues.(CVE-2024-54456)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: fix mbss changed flags corruption on 32 bit systems&lt;/p&gt;
&lt;p&gt;On 32-bit systems, the size of an unsigned long is 4 bytes,
while a u64 is 8 bytes. Therefore, when using
or_each_set_bit(bit, &amp;amp;amp;bits, sizeof(changed) * BITS_PER_BYTE),
the code is incorrectly searching for a bit in a 32-bit
variable that is expected to be 64 bits in size,
leading to incorrect bit finding.&lt;/p&gt;
&lt;p&gt;Solution: Ensure that the size of the bits variable is correctly
adjusted for each architecture.&lt;/p&gt;
&lt;p&gt;Call Trace:
  ? show_regs+0x54/0x58
  ? __warn+0x6b/0xd4
  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]
  ? report_bug+0x113/0x150
  ? exc_overflow+0x30/0x30
  ?…&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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client()&lt;/p&gt;
&lt;p&gt;name is char[64] where the size of clnt-&amp;amp;gt;cl_program-&amp;amp;gt;name remains
unknown. Invoking strcat() directly will also lead to potential buffer
overflow. Change them to strscpy() and strncat() to fix potential
issues.(CVE-2024-54456)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: fix mbss changed flags corruption on 32 bit systems&lt;/p&gt;
&lt;p&gt;On 32-bit systems, the size of an unsigned long is 4 bytes,
while a u64 is 8 bytes. Therefore, when using
or_each_set_bit(bit, &amp;amp;amp;bits, sizeof(changed) * BITS_PER_BYTE),
the code is incorrectly searching for a bit in a 32-bit
variable that is expected to be 64 bits in size,
leading to incorrect bit finding.&lt;/p&gt;
&lt;p&gt;Solution: Ensure that the size of the bits variable is correctly
adjusted for each architecture.&lt;/p&gt;
&lt;p&gt;Call Trace:
  ? show_regs+0x54/0x58
  ? __warn+0x6b/0xd4
  ? ieee80211_link_info_change_notify+0xcc/0xd4 [mac80211]
  ? report_bug+0x113/0x150
  ? exc_overflow+0x30/0x30
  ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1285</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21776</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21776</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: USB: hub: Ignore non-compliant devices with too many configs or interfaces Robert Morris created a test program which can cause usb_hub_to_struct_hub() to dereference a NULL or inappropriate pointer: Oops: general protection fault, probably for non-canonical address 0xcccccccccccccccc: 0000 [#1] SMP DEBUG_PAGEALLOC PTI CPU: 7 UID: 0 PID: 117 Comm: kworker/7:1 Not tainted 6.13.0-rc3-00017-gf44d154d6e3d #14 Hardware name: FreeBSD BHYVE/BHYVE, BIOS 14.0 10/17/2021 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_hub_adjust_deviceremovable+0x78/0x110 ... Call Trace:  &amp;lt;TASK&amp;gt;  ? die_addr+0x31/0x80  ? exc_general_protection+0x1b4/0x3c0  ? asm_exc_general_protection+0x26/0x30  ? usb_hub_adjust_deviceremovable+0x78/0x110  hub_probe+0x7c7/0xab0  usb_probe_interface+0x14b/0x350  really_probe+0xd0/0x2d0  ? __pfx___device_attach_driver+0x10/0x10  __driver_probe_device+0x6e/0x110  driver_probe_device+0x1a/0x90  __device_attach_driver+0x7e/0xc0  bus_for_each_drv+0x7f/0xd0  __device_attach+0xaa/0x1a0  bus_probe_device+0x8b/0xa0  device_add+0x62e/0x810  usb_set_configuration+0x65d/0x990  usb_generic_driver_probe+0x4b/0x70  usb_probe_device+0x36/0xd0 The cause of this error is that the device has two interfaces, and the hub driver binds to interface 1 instead of interface 0, which is where usb_hub_to_struct_hub() looks. We can prevent the problem from occurring by refusing to accept hub devices that violate the USB spec by havin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 199 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: USB: hub: Ignore non-compliant devices with too many configs or interfaces Robert Morris created a test program which can cause usb_hub_to_struct_hub() to dereference a NULL or inappropriate pointer: Oops: general protection fault, probably for non-canonical address 0xcccccccccccccccc: 0000 [#1] SMP DEBUG_PAGEALLOC PTI CPU: 7 UID: 0 PID: 117 Comm: kworker/7:1 Not tainted 6.13.0-rc3-00017-gf44d154d6e3d #14 Hardware name: FreeBSD BHYVE/BHYVE, BIOS 14.0 10/17/2021 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_hub_adjust_deviceremovable+0x78/0x110 ... Call Trace:  &amp;lt;TASK&amp;gt;  ? die_addr+0x31/0x80  ? exc_general_protection+0x1b4/0x3c0  ? asm_exc_general_protection+0x26/0x30  ? usb_hub_adjust_deviceremovable+0x78/0x110  hub_probe+0x7c7/0xab0  usb_probe_interface+0x14b/0x350  really_probe+0xd0/0x2d0  ? __pfx___device_attach_driver+0x10/0x10  __driver_probe_device+0x6e/0x110  driver_probe_device+0x1a/0x90  __device_attach_driver+0x7e/0xc0  bus_for_each_drv+0x7f/0xd0  __device_attach+0xaa/0x1a0  bus_probe_device+0x8b/0xa0  device_add+0x62e/0x810  usb_set_configuration+0x65d/0x990  usb_generic_driver_probe+0x4b/0x70  usb_probe_device+0x36/0xd0 The cause of this error is that the device has two interfaces, and the hub driver binds to interface 1 instead of interface 0, which is where usb_hub_to_struct_hub() looks. We can prevent the problem from occurring by refusing to accept hub devices that violate the USB spec by havin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21776</guid>
    </item>
  </channel>
</rss>
