{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.170-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.85-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.19.13-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  Input: uinput - fix circular locking dependency with ff-core  A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller):    ff-\u003emutex -\u003e udev-\u003emutex -\u003e input_mutex -\u003e dev-\u003emutex -\u003e ff-\u003emutex  The cycle is caused by four lock acquisition paths:  1. ff upload: input_ff_upload() holds ff-\u003emutex and calls    uinput_dev_upload_effect() -\u003e uinput_request_submit() -\u003e    uinput_request_send(), which acquires udev-\u003emutex.  2. device create: uinput_ioctl_handler() holds udev-\u003emutex and calls    uinput_create_device() -\u003e input_register_device(), which acquires    input_mutex.  3. device register: input_register_device() holds input_mutex and    calls kbd_connect() -\u003e input_register_handle(), which acquires    dev-\u003emutex.  4. evdev release: evdev_release() calls input_flush_device() under    dev-\u003emutex, which calls input_ff_flush() acquiring ff-\u003emutex.  Fix this by introducing a new state_lock spinlock to protect udev-\u003estate and udev-\u003edev access in uinput_request_send() instead of acquiring udev-\u003emutex.  The function only needs to atomically check device state and queue an input event into the ring buffer via uinput_dev_event() -- both operations are safe under a spinlock (ktime_get_ts64() and wake_up_interruptible() do not sleep).  This breaks the ff-\u003emutex -\u003e udev-\u003emutex link since a spinlock is a leaf in the lock ordering and cannot form cycles with mutexes.  To keep state transitions visible to uinput_request_send(), protect writes to udev-\u003estate in uinput_create_device() and uinput_destroy_device() with the same state_lock spinlock.  Additionally, move init_completion(\u0026request-\u003edone) from uinput_request_send() to uinput_request_submit() before uinput_request_reserve_slot().  Once the slot is allocated, uinput_flush_requests() may call complete() on it at any time from the destroy path, so the completion must be initialised before the request becomes visible.  Lock ordering after the fix:    ff-\u003emutex -\u003e state_lock (spinlock, leaf)   udev-\u003emutex -\u003e state_lock (spinlock, leaf)   udev-\u003emutex -\u003e input_mutex -\u003e dev-\u003emutex -\u003e ff-\u003emutex (no back-edge)",
  "id": "DEBIAN-CVE-2026-31667",
  "modified": "2026-09-14T16:47:47.435173200Z",
  "published": "2026-04-24T15:16:46.390Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-31667"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-31667"
  ]
}