<?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:11:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38525</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38525</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-38525</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1050 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-1050</link>
      <description>certfr-2025-avi-1050</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1050</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38525</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38525</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix irq-disabled in local_bh_enable() The rxrpc_assess_MTU_size() function calls down into the IP layer to find out the MTU size for a route.  When accepting an incoming call, this is called from rxrpc_new_incoming_call() which holds interrupts disabled across the code that calls down to it.  Unfortunately, the IP layer uses local_bh_enable() which, config dependent, throws a warning if IRQs are enabled: WARNING: CPU: 1 PID: 5544 at kernel/softirq.c:387 __local_bh_enable_ip+0x43/0xd0 ... RIP: 0010:__local_bh_enable_ip+0x43/0xd0 ... Call Trace:  &amp;lt;TASK&amp;gt;  rt_cache_route+0x7e/0xa0  rt_set_nexthop.isra.0+0x3b3/0x3f0  __mkroute_output+0x43a/0x460  ip_route_output_key_hash+0xf7/0x140  ip_route_output_flow+0x1b/0x90  rxrpc_assess_MTU_size.isra.0+0x2a0/0x590  rxrpc_new_incoming_peer+0x46/0x120  rxrpc_alloc_incoming_call+0x1b1/0x400  rxrpc_new_incoming_call+0x1da/0x5e0  rxrpc_input_packet+0x827/0x900  rxrpc_io_thread+0x403/0xb60  kthread+0x2f7/0x310  ret_from_fork+0x2a/0x230  ret_from_fork_asm+0x1a/0x30 ... hardirqs last  enabled at (23): _raw_spin_unlock_irq+0x24/0x50 hardirqs last disabled at (24): _raw_read_lock_irq+0x17/0x70 softirqs last  enabled at (0): copy_process+0xc61/0x2730 softirqs last disabled at (25): rt_add_uncached_list+0x3c/0x90 Fix this by moving the call to rxrpc_assess_MTU_size() out of rxrpc_init_peer() and further up the stack where it can be done without interrupts disabled. It shouldn&amp;#39;t…&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix irq-disabled in local_bh_enable() The rxrpc_assess_MTU_size() function calls down into the IP layer to find out the MTU size for a route.  When accepting an incoming call, this is called from rxrpc_new_incoming_call() which holds interrupts disabled across the code that calls down to it.  Unfortunately, the IP layer uses local_bh_enable() which, config dependent, throws a warning if IRQs are enabled: WARNING: CPU: 1 PID: 5544 at kernel/softirq.c:387 __local_bh_enable_ip+0x43/0xd0 ... RIP: 0010:__local_bh_enable_ip+0x43/0xd0 ... Call Trace:  &amp;lt;TASK&amp;gt;  rt_cache_route+0x7e/0xa0  rt_set_nexthop.isra.0+0x3b3/0x3f0  __mkroute_output+0x43a/0x460  ip_route_output_key_hash+0xf7/0x140  ip_route_output_flow+0x1b/0x90  rxrpc_assess_MTU_size.isra.0+0x2a0/0x590  rxrpc_new_incoming_peer+0x46/0x120  rxrpc_alloc_incoming_call+0x1b1/0x400  rxrpc_new_incoming_call+0x1da/0x5e0  rxrpc_input_packet+0x827/0x900  rxrpc_io_thread+0x403/0xb60  kthread+0x2f7/0x310  ret_from_fork+0x2a/0x230  ret_from_fork_asm+0x1a/0x30 ... hardirqs last  enabled at (23): _raw_spin_unlock_irq+0x24/0x50 hardirqs last disabled at (24): _raw_read_lock_irq+0x17/0x70 softirqs last  enabled at (0): copy_process+0xc61/0x2730 softirqs last disabled at (25): rt_add_uncached_list+0x3c/0x90 Fix this by moving the call to rxrpc_assess_MTU_size() out of rxrpc_init_peer() and further up the stack where it can be done without interrupts disabled. It shouldn&amp;#39;t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38525</guid>
    </item>
  </channel>
</rss>
