LiveActive security incident?Get immediate response
CVE Record

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

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
11

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49474 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49474Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux22c66af08230a7030bdb88accffaec3424695631, 0115a66ebb44bd9127ccb58cf43ed23c795eb1f0, bc4b08383046f3282b6fa58cfcef05bd13e52b93, 5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7, 059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75, e1dee2c1de2b4dd00eb44004a4bda6326ed07b59, e1dee2c1de2b4dd00eb44004a4bda6326ed07b59, e1dee2c1de2b4dd00eb44004a4bda6326ed07b59, e1dee2c1de2b4dd00eb44004a4bda6326ed07b59, 98ae477ed1540d3acbbf44d88ee237ad64275158, f0c389e23e2475e5837716a629c81b7a9d90cc94, 0b9da4bde0d59c61b3675bdd80a05a726beb875aunaffected
LinuxLinux5.15, 0, 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

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.