<?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>Fri, 20 Nov 2026 01:20:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-22025</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-22025</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-22025</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0368 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0368</link>
      <description>certfr-2025-avi-0368</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0368</guid>
    </item>
    <item>
      <title>OESA-2025-2802 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2802</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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&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;nfc: nci: Fix uninit-value in nci_rx_work&lt;/p&gt;
&lt;p&gt;syzbot reported the following uninit-value access issue [1]&lt;/p&gt;
&lt;p&gt;nci_rx_work() parses received packet from ndev-&amp;amp;gt;rx_q. It should be
validated header size, payload size and total packet size before
processing the packet. If an invalid packet is detected, it should be
silently discarded.(CVE-2024-38381)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2802</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-22025</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22025</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 204 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: put dl_stid if fail to queue dl_recall Before calling nfsd4_run_cb to queue dl_recall to the callback_wq, we increment the reference count of dl_stid. We expect that after the corresponding work_struct is processed, the reference count of dl_stid will be decremented through the callback function nfsd4_cb_recall_release. However, if the call to nfsd4_run_cb fails, the incremented reference count of dl_stid will not be decremented correspondingly, leading to the following nfs4_stid leak: unreferenced object 0xffff88812067b578 (size 344):   comm &amp;#34;nfsd&amp;#34;, pid 2761, jiffies 4295044002 (age 5541.241s)   hex dump (first 32 bytes):     01 00 00 00 6b 6b 6b 6b b8 02 c0 e2 81 88 ff ff  ....kkkk........     00 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 ad 4e ad de  .kkkkkkk.....N..   backtrace:     kmem_cache_alloc+0x4b9/0x700     nfsd4_process_open1+0x34/0x300     nfsd4_open+0x2d1/0x9d0     nfsd4_proc_compound+0x7a2/0xe30     nfsd_dispatch+0x241/0x3e0     svc_process_common+0x5d3/0xcc0     svc_process+0x2a3/0x320     nfsd+0x180/0x2e0     kthread+0x199/0x1d0     ret_from_fork+0x30/0x50     ret_from_fork_asm+0x1b/0x30 unreferenced object 0xffff8881499f4d28 (size 368):   comm &amp;#34;nfsd&amp;#34;, pid 2761, jiffies 4295044005 (age 5541.239s)   hex dump (first 32 bytes):     01 00 00 00 00 00 00 00 30 4d 9f 49 81 88 ff ff  ........0M.I....     30 4d 9f 49 81 88 ff ff 20 00 00 00 01 00 00 00  0M.I.... .......   backtrace:     kmem_cache_allo…&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 204 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nfsd: put dl_stid if fail to queue dl_recall Before calling nfsd4_run_cb to queue dl_recall to the callback_wq, we increment the reference count of dl_stid. We expect that after the corresponding work_struct is processed, the reference count of dl_stid will be decremented through the callback function nfsd4_cb_recall_release. However, if the call to nfsd4_run_cb fails, the incremented reference count of dl_stid will not be decremented correspondingly, leading to the following nfs4_stid leak: unreferenced object 0xffff88812067b578 (size 344):   comm &amp;#34;nfsd&amp;#34;, pid 2761, jiffies 4295044002 (age 5541.241s)   hex dump (first 32 bytes):     01 00 00 00 6b 6b 6b 6b b8 02 c0 e2 81 88 ff ff  ....kkkk........     00 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 ad 4e ad de  .kkkkkkk.....N..   backtrace:     kmem_cache_alloc+0x4b9/0x700     nfsd4_process_open1+0x34/0x300     nfsd4_open+0x2d1/0x9d0     nfsd4_proc_compound+0x7a2/0xe30     nfsd_dispatch+0x241/0x3e0     svc_process_common+0x5d3/0xcc0     svc_process+0x2a3/0x320     nfsd+0x180/0x2e0     kthread+0x199/0x1d0     ret_from_fork+0x30/0x50     ret_from_fork_asm+0x1b/0x30 unreferenced object 0xffff8881499f4d28 (size 368):   comm &amp;#34;nfsd&amp;#34;, pid 2761, jiffies 4295044005 (age 5541.239s)   hex dump (first 32 bytes):     01 00 00 00 00 00 00 00 30 4d 9f 49 81 88 ff ff  ........0M.I....     30 4d 9f 49 81 88 ff ff 20 00 00 00 01 00 00 00  0M.I.... .......   backtrace:     kmem_cache_allo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-22025</guid>
    </item>
  </channel>
</rss>
