Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89774Bluetooth: SCO: hold sk properly in sco_conn_ready

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: hold sk properly in sco_conn_ready sk deref in sco_conn_ready must be done either under conn->lock, or holding a refcount, to avoid concurrent close. conn->sk and parent sk is currently accessed without either, and without checking parent->sk_state: [Task 1] [Task 2] sco_sock_release sco_conn_ready sk = conn->sk lock_sock(sk) conn->sk = NULL lock_sock(sk) release_sock(sk) sco_sock_kill(sk) UAF on sk deref and similarly for access to sco_get_sock_listen() return value. Fix possible UAF by holding sk refcount in sco_conn_ready() and making sco_get_sock_listen() increase refcount. Also recheck after lock_sock that the socket is still valid. Adjust conn->sk locking so it's protected also by lock_sock() of the associated socket if any.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89774, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 65% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < 50aae396dc30377bec8e3b181b8346f8fd38f7d8
    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < 6e3840578aaad1a296aab1eaaa89ea3b7d5cbae1
    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < d141d9b769bcd1b747898528c5023270cda040f2
    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < 73cb063f5ec6ca51eb1e246c6d332563002ac277
    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < 7199c78c3a3e399a4dc439d845826793880ccedc
    • affected 27c24fda62b601d6f9ca5e992502578c4310876f – < 4e37f6452d586b95c346a9abdd2fb80b67794f39
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89774 badge
[![CVE-2026-89774](https://cveledger.app/badge/CVE-2026-89774.svg)](https://cveledger.app/cve/CVE-2026-89774)

Record last updated .