<?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 08:56:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-53208</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-53208</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-2024-53208</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0047 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0047</link>
      <description>certfr-2025-avi-0047</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0047</guid>
    </item>
    <item>
      <title>OESA-2025-1110 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1110</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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&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;i3c: Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock&lt;/p&gt;
&lt;p&gt;A deadlock may happen since the i3c_master_register() acquires
&amp;amp;amp;i3cbus-&amp;amp;gt;lock twice. See the log below.
Use i3cdev-&amp;amp;gt;desc-&amp;amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.&lt;/p&gt;
&lt;p&gt;v2:
  - Modified the title and commit message&lt;/p&gt;
&lt;p&gt;============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock&lt;/p&gt;
&lt;p&gt;but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:
 Possible unsafe locking scenario:&lt;/p&gt;
&lt;p&gt;CPU0
       ----
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);
  lock(&amp;amp;amp;i3cbus-&amp;amp;gt;lock);&lt;/p&gt;
&lt;p&gt;*** DEADLOCK ***&lt;/p&gt;
&lt;p&gt;May be due to missing lock nesting notation&lt;/p&gt;
&lt;p&gt;2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;amp;dev-&amp;amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;amp;i3cbus-&amp;amp;gt;lock){++++}-{3:3}, at: i3c_master_register&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 6 UID: 0 PID: 1 Comm: init
Call trace:
 dump_backtrace+0xfc/0x17c
 show_stack+0x18/0x28
 dump_stack_lvl+0x40/0xc0
 dump_stack+0x18/0x24
 print_deadlock_bug+0x388/0x390
 __lock_acquire+0x18bc/0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1110</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53208</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-53208</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: Bluetooth: MGMT: Fix slab-use-after-free Read in set_powered_sync This fixes the following crash: ================================================================== BUG: KASAN: slab-use-after-free in set_powered_sync+0x3a/0xc0 net/bluetooth/mgmt.c:1353 Read of size 8 at addr ffff888029b4dd18 by task kworker/u9:0/54 CPU: 1 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-01155-gf723224742fc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci0 hci_cmd_sync_work Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488 q kasan_report+0x143/0x180 mm/kasan/report.c:601  set_powered_sync+0x3a/0xc0 net/bluetooth/mgmt.c:1353  hci_cmd_sync_work+0x22b/0x400 net/bluetooth/hci_sync.c:328  process_one_work kernel/workqueue.c:3231 [inline]  process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312  worker_thread+0x86d/0xd10 kernel/workqueue.c:3389  kthread+0x2f0/0x390 kernel/kthread.c:389  ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  &amp;lt;/TASK&amp;gt; Allocated by task 5247:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  poison_kmalloc_redzone mm/kasan/common.c:370 [inline]  __kasa…&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: Bluetooth: MGMT: Fix slab-use-after-free Read in set_powered_sync This fixes the following crash: ================================================================== BUG: KASAN: slab-use-after-free in set_powered_sync+0x3a/0xc0 net/bluetooth/mgmt.c:1353 Read of size 8 at addr ffff888029b4dd18 by task kworker/u9:0/54 CPU: 1 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-01155-gf723224742fc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci0 hci_cmd_sync_work Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:93 [inline]  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119  print_address_description mm/kasan/report.c:377 [inline]  print_report+0x169/0x550 mm/kasan/report.c:488 q kasan_report+0x143/0x180 mm/kasan/report.c:601  set_powered_sync+0x3a/0xc0 net/bluetooth/mgmt.c:1353  hci_cmd_sync_work+0x22b/0x400 net/bluetooth/hci_sync.c:328  process_one_work kernel/workqueue.c:3231 [inline]  process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312  worker_thread+0x86d/0xd10 kernel/workqueue.c:3389  kthread+0x2f0/0x390 kernel/kthread.c:389  ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244  &amp;lt;/TASK&amp;gt; Allocated by task 5247:  kasan_save_stack mm/kasan/common.c:47 [inline]  kasan_save_track+0x3f/0x80 mm/kasan/common.c:68  poison_kmalloc_redzone mm/kasan/common.c:370 [inline]  __kasa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-53208</guid>
    </item>
  </channel>
</rss>
