Heimdall Security Logo

CVE-2026-53256

Vulnérabilité élevée dans Linux (Linux)

CVSS 8.0 · Élevée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, 2.6.12, <de31973ef00e5aa55496f84cf6a44bb157a34e02, 0, 6.1.176, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 5.15.210, <=5.10.*, <=6.6.*, 7.0.13, <b0e33e409715c617e2a20f46f99aa5403a14dfda, 6.18.36, <6f4462d12133106460d7c046b95aad2491e3fddf, <1f73f92f66251065a5f39b09a47cf05ea14d3107, 7.1, <=6.18.*, <43c441edacf953b39517a44f5e5e10a93618b226, <f5ec76bdbeb80f75ad0be204371afffee0f8fac8, <=*, <=5.15.*, 6.6.143, <8802413ce63175fb522a2bd609fb043a3550c720, <a07d741c077d4e34b16458241a94d29039386553, 5.10.259

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: hold listener socket in rfcomm_connect_ind() rfcomm_get_sock_by_channel() scans rfcomm_sk_list under the list lock, but returns the selected listener after dropping that lock without taking a reference. rfcomm_connect_ind() then locks the listener, queues a child socket on it, and may notify it after unlocking it. The buggy scenario involves two paths, with each column showing the order within that path: rfcomm_connect_ind(): listener close: 1. Find parent in 1. close() enters rfcomm_get_sock_by_channel() rfcomm_sock_release(). 2. Drop rfcomm_sk_list.lock 2. rfcomm_sock_shutdown() without pinning parent. closes the listener. 3. Call lock_sock(parent) and 3. rfcomm_sock_kill() bt_accept_enqueue(parent, unlinks and puts parent. sk, true). 4. Read parent flags and may 4. parent can be freed. call sk_state_change(). If close wins the race, parent can be freed before rfcomm_connect_ind() reaches lock_sock(), bt_accept_enqueue(), or the deferred-setup callback. Take a reference on the listener before leaving rfcomm_sk_list.lock. After lock_sock() succeeds, recheck that it is still in BT_LISTEN before queueing a child, cache the deferred-setup bit while the parent is locked, and drop the reference after the last parent use. KASAN reported a slab-use-after-free in lock_sock_nested() from rfcomm_connect_ind(), with the freeing stack going through rfcomm_sock_kill() and rfcomm_sock_release().

Gravité et risque d'exploitation

CVE-2026-53256 obtient un score CVSS de 8.0/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.26 %, ce qui la place devant 17.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 6.12.94, 2.6.12, <de31973ef00e5aa55496f84cf6a44bb157a34e02, 0, 6.1.176, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 5.15.210, <=5.10.*, <=6.6.*, 7.0.13, <b0e33e409715c617e2a20f46f99aa5403a14dfda, 6.18.36, <6f4462d12133106460d7c046b95aad2491e3fddf, <1f73f92f66251065a5f39b09a47cf05ea14d3107, 7.1, <=6.18.*, <43c441edacf953b39517a44f5e5e10a93618b226, <f5ec76bdbeb80f75ad0be204371afffee0f8fac8, <=*, <=5.15.*, 6.6.143, <8802413ce63175fb522a2bd609fb043a3550c720, <a07d741c077d4e34b16458241a94d29039386553, 5.10.259) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE