Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Bluetooth stability flaw. Certain fake CSR 5.0 clone USB Bluetooth controllers can cause duplicate suspend-notifier registration when replugged, leading to a kernel panic. The supplied sources support an availability risk, not data theft or remote compromise.
Executive priority
Treat as a targeted availability hardening item. Patch during normal maintenance unless affected systems depend on Bluetooth peripherals in production, kiosks, labs, or unattended environments where a panic would cause meaningful downtime.
Technical view
The crash occurs in the btusb Bluetooth path during device probing, with hci_register_dev calling blocking_notifier_chain_register after a fake CSR controller is reintroduced. The CVE record says the issue is resolved in Linux kernel stable commits, but provides no CVSS score or CWE classification.
Likely exposure
Exposure appears limited to Linux systems running affected kernel builds with fake CSR 5.0 clone Bluetooth controllers. Servers without Bluetooth hardware or USB peripheral attachment paths are likely less exposed, based on the provided source data.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The described condition involves replugging specific fake CSR Bluetooth controllers and results in a kernel panic, making this primarily a local availability concern.
Researcher notes
Evidence is narrow: the CVE text documents a kernel panic path and two kernel stable references, but no CVSS, CWE, broad affected matrix, or exploitation reports. Avoid expanding scope beyond Linux Bluetooth handling of fake CSR clone controllers.
Mitigation direction
Apply a vendor kernel update containing the referenced upstream stable fixes.
Prioritize Linux systems using USB Bluetooth adapters, especially CSR clone devices.
Disable or remove unneeded Bluetooth/USB peripheral access where operationally acceptable.
Check distribution advisories before relying on upstream commit IDs alone.
Validation and detection
Inventory Linux kernel versions against vendor fixed releases.
Identify systems with USB Bluetooth adapters or enabled Bluetooth support.
Review kernel logs for btusb probe failures or panic traces matching this issue.
Confirm patched kernels include the referenced stable commits or vendor backports.
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.
cve · low confidence lookup
CVE-2022-48982 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.