<?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 09:46:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38388</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38388</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-38388</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0922 — 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-0922</link>
      <description>certfr-2025-avi-0922</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0922</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38388</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38388</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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:   |  BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258   |  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0   |  preempt_count: 1, expected: 0   |  RCU nest depth: 0, expected: 0   |  CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0 #4   |  Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn   |  Call trace:   |   show_stack+0x18/0x24 (C)   |   dump_stack_lvl+0x78/0x90   |   dump_stack+0x18/0x24   |   __might_resched+0x114/0x170   |   __might_sleep+0x48/0x98   |   mutex_lock+0x24/0x80   |   handle_notif_callbacks+0x54/0xe0   |   notif_get_and_handle+0x40/0x88   |   generic_exec_single+0x80/0xc0   |   smp_call_function_single+0xfc/0x1a0   |   notif_pcpu_irq_work_fn+0x2c/0x38   |   process_one_work+0x14c/0x2b4   |   worker_thread+0x2e4/0x3e0   |   kthread+0x13c/0x210   |   ret_from_fork+0x10/0x20 To address this, replace the mutex with an rwlock to protect the notifier hashtable accesses. This ensures that read-side locking does not sleep and multiple readers can acquire the lock concurrently, avoiding unnecessary contention and potential deadlocks. Writer access remains exclusive, preserving correctness. Thi…&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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Replace mutex with rwlock to avoid sleep in atomic context The current use of a mutex to protect the notifier hashtable accesses can lead to issues in the atomic context. It results in the below kernel warnings:   |  BUG: sleeping function called from invalid context at kernel/locking/mutex.c:258   |  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 9, name: kworker/0:0   |  preempt_count: 1, expected: 0   |  RCU nest depth: 0, expected: 0   |  CPU: 0 UID: 0 PID: 9 Comm: kworker/0:0 Not tainted 6.14.0 #4   |  Workqueue: ffa_pcpu_irq_notification notif_pcpu_irq_work_fn   |  Call trace:   |   show_stack+0x18/0x24 (C)   |   dump_stack_lvl+0x78/0x90   |   dump_stack+0x18/0x24   |   __might_resched+0x114/0x170   |   __might_sleep+0x48/0x98   |   mutex_lock+0x24/0x80   |   handle_notif_callbacks+0x54/0xe0   |   notif_get_and_handle+0x40/0x88   |   generic_exec_single+0x80/0xc0   |   smp_call_function_single+0xfc/0x1a0   |   notif_pcpu_irq_work_fn+0x2c/0x38   |   process_one_work+0x14c/0x2b4   |   worker_thread+0x2e4/0x3e0   |   kthread+0x13c/0x210   |   ret_from_fork+0x10/0x20 To address this, replace the mutex with an rwlock to protect the notifier hashtable accesses. This ensures that read-side locking does not sleep and multiple readers can acquire the lock concurrently, avoiding unnecessary contention and potential deadlocks. Writer access remains exclusive, preserving correctness. Thi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38388</guid>
    </item>
  </channel>
</rss>
