{
  "cveId": "CVE-2026-46202",
  "url": "https://patchblox.com/security/cve/CVE-2026-46202",
  "summary": "CVE-2026-46202 is fixed in linux on 1 platform by DEBIAN-CVE-2026-46202 (version 7.0.9-1), released June 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  HID: appletb-kbd: run inactivity autodim from wo...",
  "description": "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 \u0022reset the inactivity timer\u0022.",
  "published": "2026-05-28T10:16:35Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00128,
  "epssPercentile": 0.02488,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.0.9-1",
      "fix": "DEBIAN-CVE-2026-46202",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-46202",
      "released": "2026-06-24T14:07:24Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}