<?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 05:53:20 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21731</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21731</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-21731</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-1245 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1245</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe()&lt;/p&gt;
&lt;p&gt;I got a null-ptr-deref report:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
...
RIP: 0010:fb_destroy_modelist+0x38/0x100
...
Call Trace:
 ufx_usb_probe.cold+0x2b5/0xac1 [smscufx]
 usb_probe_interface+0x1aa/0x3c0 [usbcore]
 really_probe+0x167/0x460
...
 ret_from_fork+0x1f/0x30&lt;/p&gt;
&lt;p&gt;If fb_alloc_cmap() fails in ufx_usb_probe(), fb_destroy_modelist() will
be called to destroy modelist in the error handling path. But modelist
has not been initialized yet, so it will result in null-ptr-deref.&lt;/p&gt;
&lt;p&gt;Initialize modelist before calling fb_alloc_cmap() to fix this bug.(CVE-2021-47652)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ata: sata_dwc_460ex: Fix crash due to OOB write&lt;/p&gt;
&lt;p&gt;the driver uses libata&amp;amp;apos;s &amp;amp;quot;tag&amp;amp;quot; values from in various arrays.
Since the mentioned patch bumped the ATA_TAG_INTERNAL to 32,
the value of the SATA_DWC_QCMD_MAX needs to account for that.&lt;/p&gt;
&lt;p&gt;Otherwise ATA_TAG_INTERNAL usage cause similar crashes like
this as reported by Tice Rex on the OpenWrt Forum and
reproduced (with symbols) here:&lt;/p&gt;
&lt;p&gt;| BUG: Kernel NULL pointer dereference at 0x00000000
| Faulting instruction address: 0xc03ed4b8
| Oops: Kernel access of bad area, sig: 11 [#1]
| BE PAGE_SIZE=4K PowerPC 44x Platform
| CPU: 0 PID: 362 Comm: scsi_eh_1 Not tainted 5.4.1…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe()&lt;/p&gt;
&lt;p&gt;I got a null-ptr-deref report:&lt;/p&gt;
&lt;p&gt;BUG: kernel NULL pointer dereference, address: 0000000000000000
...
RIP: 0010:fb_destroy_modelist+0x38/0x100
...
Call Trace:
 ufx_usb_probe.cold+0x2b5/0xac1 [smscufx]
 usb_probe_interface+0x1aa/0x3c0 [usbcore]
 really_probe+0x167/0x460
...
 ret_from_fork+0x1f/0x30&lt;/p&gt;
&lt;p&gt;If fb_alloc_cmap() fails in ufx_usb_probe(), fb_destroy_modelist() will
be called to destroy modelist in the error handling path. But modelist
has not been initialized yet, so it will result in null-ptr-deref.&lt;/p&gt;
&lt;p&gt;Initialize modelist before calling fb_alloc_cmap() to fix this bug.(CVE-2021-47652)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ata: sata_dwc_460ex: Fix crash due to OOB write&lt;/p&gt;
&lt;p&gt;the driver uses libata&amp;amp;apos;s &amp;amp;quot;tag&amp;amp;quot; values from in various arrays.
Since the mentioned patch bumped the ATA_TAG_INTERNAL to 32,
the value of the SATA_DWC_QCMD_MAX needs to account for that.&lt;/p&gt;
&lt;p&gt;Otherwise ATA_TAG_INTERNAL usage cause similar crashes like
this as reported by Tice Rex on the OpenWrt Forum and
reproduced (with symbols) here:&lt;/p&gt;
&lt;p&gt;| BUG: Kernel NULL pointer dereference at 0x00000000
| Faulting instruction address: 0xc03ed4b8
| Oops: Kernel access of bad area, sig: 11 [#1]
| BE PAGE_SIZE=4K PowerPC 44x Platform
| CPU: 0 PID: 362 Comm: scsi_eh_1 Not tainted 5.4.1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1245</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21731</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21731</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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 190 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nbd: don&amp;#39;t allow reconnect after disconnect Following process can cause nbd_config UAF: 1) grab nbd_config temporarily; 2) nbd_genl_disconnect() flush all recv_work() and release the initial reference:   nbd_genl_disconnect    nbd_disconnect_and_put     nbd_disconnect      flush_workqueue(nbd-&amp;gt;recv_workq)     if (test_and_clear_bit(NBD_RT_HAS_CONFIG_REF, ...))      nbd_config_put      -&amp;gt; due to step 1), reference is still not zero 3) nbd_genl_reconfigure() queue recv_work() again;   nbd_genl_reconfigure    config = nbd_get_config_unlocked(nbd)    if (!config)    -&amp;gt; succeed    if (!test_bit(NBD_RT_BOUND, ...))    -&amp;gt; succeed    nbd_reconnect_socket     queue_work(nbd-&amp;gt;recv_workq, &amp;amp;args-&amp;gt;work) 4) step 1) release the reference; 5) Finially, recv_work() will trigger UAF:   recv_work    nbd_config_put(nbd)    -&amp;gt; nbd_config is freed    atomic_dec(&amp;amp;config-&amp;gt;recv_threads)    -&amp;gt; UAF Fix the problem by clearing NBD_RT_BOUND in nbd_genl_disconnect(), so that nbd_genl_reconfigure() will fail.&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:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 190 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nbd: don&amp;#39;t allow reconnect after disconnect Following process can cause nbd_config UAF: 1) grab nbd_config temporarily; 2) nbd_genl_disconnect() flush all recv_work() and release the initial reference:   nbd_genl_disconnect    nbd_disconnect_and_put     nbd_disconnect      flush_workqueue(nbd-&amp;gt;recv_workq)     if (test_and_clear_bit(NBD_RT_HAS_CONFIG_REF, ...))      nbd_config_put      -&amp;gt; due to step 1), reference is still not zero 3) nbd_genl_reconfigure() queue recv_work() again;   nbd_genl_reconfigure    config = nbd_get_config_unlocked(nbd)    if (!config)    -&amp;gt; succeed    if (!test_bit(NBD_RT_BOUND, ...))    -&amp;gt; succeed    nbd_reconnect_socket     queue_work(nbd-&amp;gt;recv_workq, &amp;amp;args-&amp;gt;work) 4) step 1) release the reference; 5) Finially, recv_work() will trigger UAF:   recv_work    nbd_config_put(nbd)    -&amp;gt; nbd_config is freed    atomic_dec(&amp;amp;config-&amp;gt;recv_threads)    -&amp;gt; UAF Fix the problem by clearing NBD_RT_BOUND in nbd_genl_disconnect(), so that nbd_genl_reconfigure() will fail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21731</guid>
    </item>
  </channel>
</rss>
