{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.9-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "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-\u003eops_lock via backlight_device_set_brightness() -\u003e 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:       \u003cIRQ\u003e       __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    backlight_device_set_brightness() directly.  Cancel both works synchronously during driver tear-down alongside the existing backlight reference drop.  The semantics are unchanged (same delays, same state transitions on dim, turn-off and user activity); only the execution context of the sleeping call changes.  The timer field and callback are renamed to match their new type; reset_inactivity_timer() keeps its name because it is invoked from input event paths that read naturally as \"reset the inactivity timer\".",
  "id": "DEBIAN-CVE-2026-46202",
  "modified": "2026-09-14T16:47:42.888168938Z",
  "published": "2026-05-28T10:16:35.860Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-46202"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-46202"
  ]
}