BaselineWatch
Desk

CVE-2026-98290

7.5 high Published

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid socket lock inversion in listener cleanup rfcomm_sock_cleanup_listen() closes unaccepted child sockets through rfcomm_sock_close(), which takes the child socket lock before rfcomm_dlc_close() acquires rfcomm_mutex. The RFCOMM worker takes these locks in reverse order while handling connections and DLC state changes, so lockdep reports a possible deadlock. Close dequeued children without taking their socket lock. The accept queue owns a reference to each child, and bt_accept_dequeue() locks the child while unlinking it and clearing its parent pointer. Dropping the child lock makes it important to prevent a concurrent rfcomm_connect_ind() from enqueueing a new child after cleanup observes an empty queue. Set a listening socket to BT_CLOSED while its lock is still held, before dropping the lock and draining the queue. The state check in rfcomm_connect_ind() then rejects new children once cleanup starts.

Fix

Microsoft's update · Moderate

  • Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.158.1-1

From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-31.

Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.

Change history 2

  1. StatusReceived → PublishedNVD modified 2026-10-19 09:17
  2. First seenCVSS 7.5NVD modified 2026-10-19 10:18

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 7