How severe is CVE-2023-53520?

This vulnerability has a CVSS score of (Unknown severity).

How difficult is it to exploit CVE-2023-53520?

Exploit difficulty: HARD. Estimated time to exploit: > 4 hours. Required skills: Advanced security expertise.

CVE-2023-53520 - YourPassGen

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:
[102152.653246] Call Trace:
[102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth]
[102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth]
[102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth]
[102152.653268] notifier_call_chain+0x43/0x6b
[102152.653271] __blocking_notifier_call_chain+0x48/0x69
[102152.653273] __pm_notifier_call_chain+0x22/0x39
[102152.653276] pm_suspend+0x287/0x57c
[102152.653278] state_store+0xae/0xe5
[102152.653281] kernfs_fop_write+0x109/0x173
[102152.653284] __vfs_write+0x16f/0x1a2
[102152.653287] ? selinux_file_permission+0xca/0x16f
[102152.653289] ? security_file_permission+0x36/0x109
[102152.653291] vfs_write+0x114/0x21d
[102152.653293] __x64_sys_write+0x7b/0xdb
[102152.653296] do_syscall_64+0x59/0x194
[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.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2023-53520

CVE-2023-53520 is a unknown severity vulnerability affecting the affected product.

Description: 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: [102152.653246] Call Trace: [102152.653254] hci_suspend_sync+0x109/0x301 [bluetooth] [102152.653259] hci_suspend_dev+0x78/0xcd [bluetooth] [102152.653263] hci_suspend_notifier+0x42/0x7a [bluetooth] [102152.653268] notifier_call_chain+0x43/0x6b [102152.653271] __blocking_notifier_call_chain+0x48/0x69 [102152.653273] […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Full CVE details

Exploit Difficulty Assessment

HARD

⏱️ Time to Exploit: > 4 hours

🛠️ Skills Required: Advanced security expertise

💰 Public Exploits: Rare or not public

Vulnerability Timeline

Oct 01, 2025

Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025

Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.

No related CVEs found (no vendor/product data available).