LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53520: Bluetooth: Fix hci_suspend_sync crash

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hci_suspend_sync crash If hci_unregister_dev() frees the hci_dev object but hci_suspend_notifier may still be accessing it, it can cause the program to crash. Here's the call trace: <4>[102152.653246] Call Trace: <4>[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth] <4>[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth] <4>[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth] <4>[102152.653268] notifier_call_chain+0x43/0x6b <4>[102152.653271] __blocking_notifier_call_chain+0x48/0x69 <4>[102152.653273] __pm_notifier_call_chain+0x22/0x39 <4>[102152.653276] pm_suspend+0x287/0x57c <4>[102152.653278] state_store+0xae/0xe5 <4>[102152.653281] kernfs_fop_write+0x109/0x173 <4>[102152.653284] __vfs_write+0x16f/0x1a2 <4>[102152.653287] ? selinux_file_permission+0xca/0x16f <4>[102152.653289] ? security_file_permission+0x36/0x109 <4>[102152.653291] vfs_write+0x114/0x21d <4>[102152.653293] __x64_sys_write+0x7b/0xdb <4>[102152.653296] do_syscall_64+0x59/0x194 <4>[102152.653299] entry_SYSCALL_64_after_hwframe+0x5c/0xc1 This patch holds the reference count of the hci_dev object while processing it in hci_suspend_notifier to avoid potential crash caused by the race condition.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Bluetooth crash bug. A race condition can let suspend handling use a Bluetooth device object after it was freed, causing the system to crash. The public record does not provide CVSS, CWE, or evidence of active exploitation.

Executive priority

Treat this as an availability and stability risk, not a confirmed widespread attack emergency. Patch through normal kernel maintenance, prioritizing Bluetooth-enabled endpoints where unexpected crashes affect operations or user productivity.

Technical view

The issue is in Linux Bluetooth suspend handling. hci_unregister_dev() can free an hci_dev while hci_suspend_notifier is still processing it. The fix keeps a reference to hci_dev during notifier processing, avoiding a race-driven crash in hci_suspend_sync.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions or unfixed downstream kernels with Bluetooth enabled. The source lists Linux 5.7 and ranges through 5.15.199, 6.1.55, 6.5.5, and 6.6 as affected, but distro backport status must be verified.

Exploitation context

No KEV listing is present, and the provided sources do not claim active exploitation. The evidence describes a kernel crash during suspend-related notifier handling, not a public exploit or remote attack path.

Researcher notes

The public record lacks CVSS, CWE, exploitability analysis, and vendor package mapping. Analysis should focus on the hci_dev lifetime race between unregister and suspend notifier paths, and on confirming downstream backports rather than assuming version strings alone.

Mitigation direction

  • Inventory Linux hosts running affected kernel branches and Bluetooth support.
  • Update through your Linux vendor to kernels containing the referenced stable fixes.
  • Track vendor advisories for exact package versions and backports.
  • Prioritize laptops, workstations, and devices using suspend or Bluetooth workflows.

Validation and detection

  • Confirm deployed kernels include one of the referenced stable commits or vendor backports.
  • Review kernel logs for Bluetooth hci_suspend_sync crash traces.
  • Test suspend and resume on representative patched systems.
  • Verify asset inventory no longer shows unfixed affected kernel versions.
Prepared
Confidence
medium
Sources
6

Public sources used

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-2023-53520 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9952d90ea2885d7cbf80cd233f694f09a9c0eaec, 9952d90ea2885d7cbf80cd233f694f09a9c0eaec, 9952d90ea2885d7cbf80cd233f694f09a9c0eaec, 9952d90ea2885d7cbf80cd233f694f09a9c0eaecunaffected
LinuxLinux5.7, 0, 5.15.199, 6.1.55, 6.5.5, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.