CVE-2022-49474: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
Connecting the same socket twice consecutively in sco_sock_connect()
could lead to a race condition where two sco_conn objects are created
but only one is associated with the socket. If the socket is closed
before the SCO connection is established, the timer associated with the
dangling sco_conn object won't be canceled. As the sock object is being
freed, the use-after-free problem happens when the timer callback
function sco_sock_timeout() accesses the socket. Here's the call trace:
dump_stack+0x107/0x163
? refcount_inc+0x1c/
print_address_description.constprop.0+0x1c/0x47e
? refcount_inc+0x1c/0x7b
kasan_report+0x13a/0x173
? refcount_inc+0x1c/0x7b
check_memory_region+0x132/0x139
refcount_inc+0x1c/0x7b
sco_sock_timeout+0xb2/0x1ba
process_one_work+0x739/0xbd1
? cancel_delayed_work+0x13f/0x13f
? __raw_spin_lock_init+0xf0/0xf0
? to_kthread+0x59/0x85
worker_thread+0x593/0x70e
kthread+0x346/0x35a
? drain_workqueue+0x31a/0x31a
? kthread_bind+0x4b/0x4b
ret_from_fork+0x1f/0x30
Security readout for executives and security teams
Plain-English summary
CVE-2022-49474 is a Linux kernel Bluetooth flaw. A local low-privileged user can trigger a race in SCO socket connection handling that may cause use-after-free memory corruption. The CVSS rating is high because successful exploitation could affect confidentiality, integrity, and availability on an affected host.
Executive priority
Prioritize remediation where untrusted local users, shared access, or Bluetooth-enabled Linux endpoints exist. Internet-facing exposure is not indicated by the source bundle, but local kernel flaws can still become serious in chained attacks.
Technical view
The issue is a CWE-416 use-after-free in Linux Bluetooth SCO handling. Repeated sco_sock_connect() calls can create a dangling sco_conn whose timer is not canceled when the socket closes. The sco_sock_timeout() callback can later access freed socket memory. Kernel stable commits are listed as fixes.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions with Bluetooth/SCO functionality present. The source lists Linux kernel version ranges and stable fix commits, but distribution-specific package backport status must be verified with each vendor.
Exploitation context
The CVSS vector is local, low complexity, low privileges, and no user interaction. The bundle does not show CISA KEV listing or any cited evidence of active exploitation. Treat this as a local privilege-risk kernel memory corruption issue, not a confirmed exploited-in-the-wild vulnerability.
Researcher notes
The provided evidence supports a Bluetooth SCO race leading to dangling sco_conn and timer callback use-after-free. Affected-version data in the bundle is not enough to map every distro package precisely. Validate through vendor advisories, kernel changelogs, and the referenced stable commits.
Mitigation direction
Apply vendor Linux kernel updates that include the referenced stable fixes.
Verify distro backport advisories before relying on upstream version numbers alone.
Where vendor-approved, disable unused Bluetooth functionality until patched.
Prioritize shared workstations, developer machines, and multi-user Linux servers.
Track kernel reboot completion after patch deployment.
Validation and detection
Inventory Linux kernel versions across endpoints and servers.
Check whether Bluetooth modules or services are present and enabled.
Compare installed kernels against vendor advisories and referenced stable commits.
Confirm patched hosts have rebooted into the updated kernel.
Review vulnerability scanner findings for distro-specific backport awareness.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.