https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 20:49:06 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46202 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>HID: appletb-kbd: run inactivity autodim from workqueues</p> <p>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:</p> <p>* appletb_inactivity_timer() is a struct timer_list callback, so it runs in softirq context. Every expiry triggers</p> <p>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</p> <p>* 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.</p> <p>Both call sites hit the same mutex_lock()-from-atomic bug. Fix them together by moving the blocking work onto the system workqueue:</p> <p>* 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 c…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>HID: appletb-kbd: run inactivity autodim from workqueues</p> <p>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:</p> <p>* appletb_inactivity_timer() is a struct timer_list callback, so it runs in softirq context. Every expiry triggers</p> <p>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</p> <p>* 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.</p> <p>Both call sites hit the same mutex_lock()-from-atomic bug. Fix them together by moving the blocking work onto the system workqueue:</p> <p>* 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 c…</p> https://vulnerability.circl.lu/vuln/cve-2026-46202