<?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-21T11:54:52.889209+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-2026-46202</id>
    <title>BELL-CVE-2026-46202</title>
    <updated>2026-11-21T11:54:52.896931+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-46202"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</id>
    <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T11:54:52.896978+00:00</updated>
    <content>certfr-2026-avi-0926</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0926"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46202</id>
    <title>UBUNTU-CVE-2026-46202</title>
    <updated>2026-11-21T11:54:52.896995+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 124 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: HID: appletb-kbd: run inactivity autodim from workqueues The autodim code in hid-appletb-kbd takes backlight_device-&gt;ops_lock via backlight_device_set_brightness() -&gt; mutex_lock() from two different atomic contexts:  * appletb_inactivity_timer() is a struct timer_list callback, so it    runs in softirq context.  Every expiry triggers      BUG: sleeping function called from invalid context at kernel/locking/mutex.c:591      Call Trace:       &lt;IRQ&gt;       __might_resched       __mutex_lock       backlight_device_set_brightness       appletb_inactivity_timer       call_timer_fn       run_timer_softirq  * reset_inactivity_timer() is called from appletb_kbd_hid_event() and    appletb_kbd_inp_event().  On real USB hardware these run in    softirq/IRQ context (URB completion and input-event dispatch).    When the Touch Bar has already been dimmed or turned off, the    reset path calls backlight_device_set_brightness() directly to    restore brightness, producing the same warning. Both call sites hit the same mutex_lock()-from-atomic bug.  Fix them together by moving the blocking work onto the system workqueue:  * Convert the inactivity timer from struct timer_list to    struct delayed_work; the callback (appletb_inactivity_work) now    runs in process context where mutex_lock() is legal.  * Add a dedicated struct work_struct restore_brightness_work and have    reset_inactivity_timer() schedule it instead of calling…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46202"/>
  </entry>
</feed>
