<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T19:43:20.201158+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2025-21645</id>
    <title>BELL-CVE-2025-21645</title>
    <updated>2026-11-19T19:43:20.254842+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-21645"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</id>
    <title>certfr-2025-avi-0088 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-19T19:43:20.254877+00:00</updated>
    <content>certfr-2025-avi-0088</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0088"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1110</id>
    <title>OESA-2025-1110 — kernel security update</title>
    <updated>2026-11-19T19:43:20.254889+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>i3c: Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_get_info() to avoid deadlock</p>
<p>A deadlock may happen since the i3c_master_register() acquires
&amp;amp;i3cbus-&amp;gt;lock twice. See the log below.
Use i3cdev-&amp;gt;desc-&amp;gt;info instead of calling i3c_device_info() to
avoid acquiring the lock twice.</p>
<p>v2:
  - Modified the title and commit message</p>
<p>============================================
WARNING: possible recursive locking detected
6.11.0-mainline
--------------------------------------------
init/1 is trying to acquire lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_bus_normaluse_lock</p>
<p>but task is already holding lock:
f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register</p>
<p>other info that might help us debug this:
 Possible unsafe locking scenario:</p>
<p>CPU0
       ----
  lock(&amp;amp;i3cbus-&amp;gt;lock);
  lock(&amp;amp;i3cbus-&amp;gt;lock);</p>
<p>*** DEADLOCK ***</p>
<p>May be due to missing lock nesting notation</p>
<p>2 locks held by init/1:
 #0: fcffff809b6798f8 (&amp;amp;dev-&amp;gt;mutex){....}-{3:3}, at: __driver_attach
 #1: f1ffff80a6a40dc0 (&amp;amp;i3cbus-&amp;gt;lock){++++}-{3:3}, at: i3c_master_register</p>
<p>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…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1110"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21645</id>
    <title>UBUNTU-CVE-2025-21645</title>
    <updated>2026-11-19T19:43:20.255023+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 144 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it Wakeup for IRQ1 should be disabled only in cases where i8042 had actually enabled it, otherwise "wake_depth" for this IRQ will try to drop below zero and there will be an unpleasant WARN() logged: kernel: atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug kernel: ------------[ cut here ]------------ kernel: Unbalanced IRQ 1 wake disable kernel: WARNING: CPU: 10 PID: 6431 at kernel/irq/manage.c:920 irq_set_irq_wake+0x147/0x1a0 The PMC driver uses DEFINE_SIMPLE_DEV_PM_OPS() to define its dev_pm_ops which sets amd_pmc_suspend_handler() to the .suspend, .freeze, and .poweroff handlers. i8042_pm_suspend(), however, is only set as the .suspend handler. Fix the issue by call PMC suspend handler only from the same set of dev_pm_ops handlers as i8042_pm_suspend(), which currently means just the .suspend handler. To reproduce this issue try hibernating (S4) the machine after a fresh boot without putting it into s2idle first. [ij: edited the commit message.]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21645"/>
  </entry>
</feed>
