<?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 06:03:05 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39773</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39773</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-39773</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — 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-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>OESA-2025-2348 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2348</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&amp;amp;apos;s JSM serial driver, a resource leak vulnerability exists in the probe function. The error path needs to properly unwind instead of just returning directly, which may lead to resource leakage issues.(CVE-2022-50312)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rapidio: fix possible name leaks when rio_add_device() fails&lt;/p&gt;
&lt;p&gt;Patch series &amp;amp;quot;rapidio: fix three possible memory leaks&amp;amp;quot;.&lt;/p&gt;
&lt;p&gt;This patchset fixes three name leaks in error handling.
 - patch #1 fixes two name leaks while rio_add_device() fails.
 - patch #2 fixes a name leak while  rio_register_mport() fails.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;If rio_add_device() returns error, the name allocated by dev_set_name()
need be freed.  It should use put_device() to give up the reference in the
error path, so that the name can be freed in kobject_cleanup(), and the
&amp;amp;apos;rdev&amp;amp;apos; can be freed in rio_release_dev().(CVE-2022-50343)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, there is a memory leak vulnerability in the tpm_crb driver. In the crb_acpi_add() function, after obtaining the TPM2 table to retrieve information such as startup methods and assigning them to private data, the TPM2 table is no longer used after initialization is completed, but is not released correctly, resulting in memory leaks.(CVE-2022-50389)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: avoid deadlock in fs reclaim with page write…&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&amp;amp;apos;s JSM serial driver, a resource leak vulnerability exists in the probe function. The error path needs to properly unwind instead of just returning directly, which may lead to resource leakage issues.(CVE-2022-50312)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rapidio: fix possible name leaks when rio_add_device() fails&lt;/p&gt;
&lt;p&gt;Patch series &amp;amp;quot;rapidio: fix three possible memory leaks&amp;amp;quot;.&lt;/p&gt;
&lt;p&gt;This patchset fixes three name leaks in error handling.
 - patch #1 fixes two name leaks while rio_add_device() fails.
 - patch #2 fixes a name leak while  rio_register_mport() fails.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;If rio_add_device() returns error, the name allocated by dev_set_name()
need be freed.  It should use put_device() to give up the reference in the
error path, so that the name can be freed in kobject_cleanup(), and the
&amp;amp;apos;rdev&amp;amp;apos; can be freed in rio_release_dev().(CVE-2022-50343)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, there is a memory leak vulnerability in the tpm_crb driver. In the crb_acpi_add() function, after obtaining the TPM2 table to retrieve information such as startup methods and assigning them to private data, the TPM2 table is no longer used after initialization is completed, but is not released correctly, resulting in memory leaks.(CVE-2022-50389)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ext4: avoid deadlock in fs reclaim with page write…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2348</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39773</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39773</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 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable &amp;#39;time&amp;#39; in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue.   watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66]   CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none)   Call Trace:    &amp;lt;IRQ&amp;gt;    __netdev_alloc_skb+0x2e/0x3a0    br_ip6_multicast_alloc_query+0x212/0x1b70    __br_multicast_send_query+0x376/0xac0    br_multicast_send_query+0x299/0x510    br_multicast_query_expired.constprop.0+0x16d/0x1b0    call_timer_fn+0x3b/0x2a0    __run_timers+0x619/0x950    run_timer_softirq+0x11c/0x220    handle_softirqs+0x18e/0x560    __irq_exit_rcu+0x158/0x1a0    sysvec_apic_timer_interrupt+0x76/0x90    &amp;lt;/IRQ&amp;gt; This issue can be reproduced with:   ip link add br0 type bridge   echo 1 &amp;gt; /sys/class/net/br0/bridge/multicast_querier   echo 0xffffffffffffffff &amp;gt;   	/sys/class/net/br0/bridge/multicast_query_interval   ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a (&amp;#34;net: bridge: mcast: add and enforce query interval minimum&amp;#34;), add check for the query interval maximum to fix this issue.&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 216 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable &amp;#39;time&amp;#39; in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue.   watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66]   CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none)   Call Trace:    &amp;lt;IRQ&amp;gt;    __netdev_alloc_skb+0x2e/0x3a0    br_ip6_multicast_alloc_query+0x212/0x1b70    __br_multicast_send_query+0x376/0xac0    br_multicast_send_query+0x299/0x510    br_multicast_query_expired.constprop.0+0x16d/0x1b0    call_timer_fn+0x3b/0x2a0    __run_timers+0x619/0x950    run_timer_softirq+0x11c/0x220    handle_softirqs+0x18e/0x560    __irq_exit_rcu+0x158/0x1a0    sysvec_apic_timer_interrupt+0x76/0x90    &amp;lt;/IRQ&amp;gt; This issue can be reproduced with:   ip link add br0 type bridge   echo 1 &amp;gt; /sys/class/net/br0/bridge/multicast_querier   echo 0xffffffffffffffff &amp;gt;   	/sys/class/net/br0/bridge/multicast_query_interval   ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a (&amp;#34;net: bridge: mcast: add and enforce query interval minimum&amp;#34;), add check for the query interval maximum to fix this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39773</guid>
    </item>
  </channel>
</rss>
