<?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:44:48 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21650</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21650</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-21650</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — 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-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>OESA-2025-1246 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1246</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;af_packet: avoid erroring out after sock_init_data() in packet_create()&lt;/p&gt;
&lt;p&gt;After sock_init_data() the allocated sk object is attached to the provided
sock object. On error, packet_create() frees the sk object leaving the
dangling pointer in the sock object on return. Some other code may try
to use this pointer and cause use-after-free.(CVE-2024-56606)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: imu: kmx61: fix information leak in triggered buffer&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;buffer&amp;amp;apos; local array is used to push data to user space from a
triggered buffer, but it does not set values for inactive channels, as
it only uses iio_for_each_active_channel() to assign new values.&lt;/p&gt;
&lt;p&gt;Initialize the array to zero before using it to avoid pushing
uninitialized information to userspace.(CVE-2024-57908)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: pressure: zpa2326: fix information leak in triggered buffer&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;sample&amp;amp;apos; local struct is used to push data to user space from a
triggered buffer, but it has a hole between the temperature and the
timestamp (u32 pressure, u16 temperature, GAP, u64 timestamp).
This hole is never initialized.&lt;/p&gt;
&lt;p&gt;Initialize the struct to zero before using it to avoid pushing
uninitialized information to userspace.(CVE-2024-57912)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerabil…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;af_packet: avoid erroring out after sock_init_data() in packet_create()&lt;/p&gt;
&lt;p&gt;After sock_init_data() the allocated sk object is attached to the provided
sock object. On error, packet_create() frees the sk object leaving the
dangling pointer in the sock object on return. Some other code may try
to use this pointer and cause use-after-free.(CVE-2024-56606)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: imu: kmx61: fix information leak in triggered buffer&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;buffer&amp;amp;apos; local array is used to push data to user space from a
triggered buffer, but it does not set values for inactive channels, as
it only uses iio_for_each_active_channel() to assign new values.&lt;/p&gt;
&lt;p&gt;Initialize the array to zero before using it to avoid pushing
uninitialized information to userspace.(CVE-2024-57908)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: pressure: zpa2326: fix information leak in triggered buffer&lt;/p&gt;
&lt;p&gt;The &amp;amp;apos;sample&amp;amp;apos; local struct is used to push data to user space from a
triggered buffer, but it has a hole between the temperature and the
timestamp (u32 pressure, u16 temperature, GAP, u64 timestamp).
This hole is never initialized.&lt;/p&gt;
&lt;p&gt;Initialize the struct to zero before using it to avoid pushing
uninitialized information to userspace.(CVE-2024-57912)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerabil…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1246</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21650</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21650</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue The TQP BAR space is divided into two segments. TQPs 0-1023 and TQPs 1024-1279 are in different BAR space addresses. However, hclge_fetch_pf_reg does not distinguish the tqp space information when reading the tqp space information. When the number of TQPs is greater than 1024, access bar space overwriting occurs. The problem of different segments has been considered during the initialization of tqp.io_base. Therefore, tqp.io_base is directly used when the queue is read in hclge_fetch_pf_reg. The error message: Unable to handle kernel paging request at virtual address ffff800037200000 pc : hclge_fetch_pf_reg+0x138/0x250 [hclge] lr : hclge_get_regs+0x84/0x1d0 [hclge] Call trace:  hclge_fetch_pf_reg+0x138/0x250 [hclge]  hclge_get_regs+0x84/0x1d0 [hclge]  hns3_get_regs+0x2c/0x50 [hns3]  ethtool_get_regs+0xf4/0x270  dev_ethtool+0x674/0x8a0  dev_ioctl+0x270/0x36c  sock_do_ioctl+0x110/0x2a0  sock_ioctl+0x2ac/0x530  __arm64_sys_ioctl+0xa8/0x100  invoke_syscall+0x4c/0x124  el0_svc_common.constprop.0+0x140/0x15c  do_el0_svc+0x30/0xd0  el0_svc+0x1c/0x2c  el0_sync_handler+0xb0/0xb4  el0_sync+0x168/0x180&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: hns3: fixed hclge_fetch_pf_reg accesses bar space out of bounds issue The TQP BAR space is divided into two segments. TQPs 0-1023 and TQPs 1024-1279 are in different BAR space addresses. However, hclge_fetch_pf_reg does not distinguish the tqp space information when reading the tqp space information. When the number of TQPs is greater than 1024, access bar space overwriting occurs. The problem of different segments has been considered during the initialization of tqp.io_base. Therefore, tqp.io_base is directly used when the queue is read in hclge_fetch_pf_reg. The error message: Unable to handle kernel paging request at virtual address ffff800037200000 pc : hclge_fetch_pf_reg+0x138/0x250 [hclge] lr : hclge_get_regs+0x84/0x1d0 [hclge] Call trace:  hclge_fetch_pf_reg+0x138/0x250 [hclge]  hclge_get_regs+0x84/0x1d0 [hclge]  hns3_get_regs+0x2c/0x50 [hns3]  ethtool_get_regs+0xf4/0x270  dev_ethtool+0x674/0x8a0  dev_ioctl+0x270/0x36c  sock_do_ioctl+0x110/0x2a0  sock_ioctl+0x2ac/0x530  __arm64_sys_ioctl+0xa8/0x100  invoke_syscall+0x4c/0x124  el0_svc_common.constprop.0+0x140/0x15c  do_el0_svc+0x30/0xd0  el0_svc+0x1c/0x2c  el0_sync_handler+0xb0/0xb4  el0_sync+0x168/0x180&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21650</guid>
    </item>
  </channel>
</rss>
