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

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00007.

Exploitation none

Automatable no

Technical Impact partial

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
Linux Linux unaffected
Version Status Constraints
e64c97b53bc6727aa4385535166aaa047281e02d affected
< 8a66c3a94285552f6a8e45d73b34ebbad11d388b
e64c97b53bc6727aa4385535166aaa047281e02d affected
< 2c6cf0afc3856359e620e96edd952457d258e16c
e64c97b53bc6727aa4385535166aaa047281e02d affected
< e7b950458156d410509a08c41930b75e72985938
e64c97b53bc6727aa4385535166aaa047281e02d affected
< edf7284a98296369dd0891a0457eec37df244873
e64c97b53bc6727aa4385535166aaa047281e02d affected
< 5ecf7cd6fde5e72c87122084cf00d63e35d8dd9f
e64c97b53bc6727aa4385535166aaa047281e02d affected
< 2f3957c7eb4e07df944169a3e50a4d6790e1c744
Linux Linux affected
Version Status Constraints
4.9 affected
—
0 unaffected
< 4.9
4.19.269 unaffected
≤ 4.19.*
5.4.227 unaffected
≤ 5.4.*
5.10.159 unaffected
≤ 5.10.*
5.15.83 unaffected
≤ 5.15.*
6.0.13 unaffected
≤ 6.0.*
6.1 unaffected
≤ *

Configuration 1 [-]

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc8:*:*:*:*:*:*

No data.

No data.

Subscriptions

Vendors Products
Linux Subscribe
Linux Kernel Subscribe

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://git.kernel.org/stable/c/2c6cf0afc3856359e620e96edd952457d258e16c cve-icon cve-icon
https://git.kernel.org/stable/c/2f3957c7eb4e07df944169a3e50a4d6790e1c744 cve-icon cve-icon
https://git.kernel.org/stable/c/5ecf7cd6fde5e72c87122084cf00d63e35d8dd9f cve-icon cve-icon
https://git.kernel.org/stable/c/8a66c3a94285552f6a8e45d73b34ebbad11d388b cve-icon cve-icon
https://git.kernel.org/stable/c/e7b950458156d410509a08c41930b75e72985938 cve-icon cve-icon
https://git.kernel.org/stable/c/edf7284a98296369dd0891a0457eec37df244873 cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2024102144-CVE-2022-48971-6025@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2022-48971 cve-icon
https://www.cve.org/CVERecord?id=CVE-2022-48971 cve-icon
History

Mon, 28 Oct 2024 06:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-459

Fri, 25 Oct 2024 15:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.1:rc8:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel

Tue, 22 Oct 2024 14:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 22 Oct 2024 13:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Mon, 21 Oct 2024 20:15:00 +0000

Type Values Removed Values Added
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
Title Bluetooth: Fix not cleanup led when bt_init fails
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2025-05-04T08:27:10.417Z

Reserved: 2024-08-22T01:27:53.629Z

Link: CVE-2022-48971

cve-icon Vulnrichment

Updated: 2024-10-22T13:19:11.542Z

cve-icon NVD

Status : Analyzed

Published: 2024-10-21T20:15:09.260

Modified: 2024-10-25T15:23:38.807

Link: CVE-2022-48971

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-10-21T00:00:00Z

Links: CVE-2022-48971 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses