Bug 2348005 (CVE-2022-49555) - CVE-2022-49555 kernel: Bluetooth: hci_qca: Use del_timer_sync() before freeing
Summary: CVE-2022-49555 kernel: Bluetooth: hci_qca: Use del_timer_sync() before freeing
Keywords:
Status: NEW
Alias: CVE-2022-49555
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-26 03:14 UTC by OSIDB Bzimport
Modified: 2025-02-26 18:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-26 03:14:17 UTC
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().

Comment 1 Avinash Hanwate 2025-02-26 13:49:49 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022616-CVE-2022-49555-64d2@gregkh/T

Comment 4 Avinash Hanwate 2025-02-26 18:02:13 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022616-CVE-2022-49555-64d2@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.