CVE-2022-48971
Bluetooth: Fix not cleanup led when bt_init fails
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix not cleanup led when bt_init fails bt_init() calls bt_leds_init() to register led, but if it fails later, bt_leds_cleanup() is not called to unregister it. This can cause panic if the argument "bluetooth-power" in text is freed and then another led_trigger_register() tries to access it: BUG: unable to handle page fault for address: ffffffffc06d3bc0 RIP: 0010:strcmp+0xc/0x30 Call Trace: <TASK> led_trigger_register+0x10d/0x4f0 led_trigger_register_simple+0x7d/0x100 bt_init+0x39/0xf7 [bluetooth] do_one_initcall+0xd0/0x4e0
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < 8a66c3a94285552f6a8e45d73b34ebbad11d388b
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < 2c6cf0afc3856359e620e96edd952457d258e16c
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < e7b950458156d410509a08c41930b75e72985938
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < edf7284a98296369dd0891a0457eec37df244873
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < 5ecf7cd6fde5e72c87122084cf00d63e35d8dd9f
- affected e64c97b53bc6727aa4385535166aaa047281e02d – < 2f3957c7eb4e07df944169a3e50a4d6790e1c744
- affected 4.9
- unaffected < 4.9
- unaffected 4.19.269 – ≤ 4.19.*
- unaffected 5.4.227 – ≤ 5.4.*
- unaffected 5.10.159 – ≤ 5.10.*
- unaffected 5.15.83 – ≤ 5.15.*
- unaffected 6.0.13 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (6)
- https://git.kernel.org/stable/c/8a66c3a94285552f6a8e45d73b34ebbad11d388b (opens in a new tab)
- https://git.kernel.org/stable/c/2c6cf0afc3856359e620e96edd952457d258e16c (opens in a new tab)
- https://git.kernel.org/stable/c/e7b950458156d410509a08c41930b75e72985938 (opens in a new tab)
- https://git.kernel.org/stable/c/edf7284a98296369dd0891a0457eec37df244873 (opens in a new tab)
- https://git.kernel.org/stable/c/5ecf7cd6fde5e72c87122084cf00d63e35d8dd9f (opens in a new tab)
- https://git.kernel.org/stable/c/2f3957c7eb4e07df944169a3e50a4d6790e1c744 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48971)Record last updated .