CVE-2022-49555

Bluetooth: hci_qca: Use del_timer_sync() before freeing

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 02:14 AM UTC

Updated: August 5, 2026 at 09:24 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_qca: Use del_timer_sync() before freeing While looking at a crash report on a timer list being corrupted, which usually happens when a timer is freed while still active. This is commonly triggered by code calling del_timer() instead of del_timer_sync() just before freeing. One possible culprit is the hci_qca driver, which does exactly that. Eric mentioned that wake_retrans_timer could be rearmed via the work queue, so also move the destruction of the work queue before del_timer_sync().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.3 ≤ v < 5.10.1204.3 ≤ v < 5.15.454.3 ≤ v < 5.17.134.3 ≤ v < 5.18.24.3 ≤ v < 5.195.11 ≤ v < 5.15.455.16 ≤ v < 5.17.135.18 ≤ v < 5.18.20ff252c1976da5d80db1377eb39b551931e618264.3

Vendor states this is fixed in 2717654ae022e6ea959a4b7b762702fe1a4690c2 (fixed)

Vendor states this is fixed in 37d17f63d085d601011964ade7371aeebeb6ed4b (fixed)

Vendor states this is fixed in 4989bb03342941f2b730b37dfa38bce27b543661 (fixed)

Vendor states this is fixed in 72ef98445aca568a81c2da050532500a8345ad3a (fixed)

Vendor states this is fixed in db03727b4bbbbb36e6ef4cb655c670eefb6448e9 (fixed)

Vendor states this is fixed in 4.3 (unaffected)

Vendor states this is fixed in 5.10.120 (unaffected)

Vendor states this is fixed in 5.15.45 (unaffected)

Vendor states this is fixed in 5.17.13 (unaffected)

Vendor states this is fixed in 5.18.2 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)