CVE-2023-54164

HIGHPre-NVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. the CNA's CVSS baseline 8.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: ISO: fix iso_conn related locking and validity issues

sk->sk_state indicates whether iso_pi(sk)->conn is valid. Operations that check/update sk_state and access conn should hold lock_sock, otherwise they can race.

The order of taking locks is hci_dev_lock > lock_sock > iso_conn_lock, which is how it is in connect/disconnect_cfm -> iso_conn_del -> iso_chan_del.

Fix locking in iso_connect_cis/bis and sendmsg/recvmsg to take lock_sock around updating sk_state and conn.

iso_conn_del must not occur during iso_connect_cis/bis, as it frees the iso_conn. Hold hdev->lock longer to prevent that.

This should not reintroduce the issue fixed in commit 241f51931c35 ("Bluetooth: ISO: Avoid circular locking dependency"), since the we acquire locks in order. We retain the fix in iso_sock_connect to release lock_sock before iso_connect_* acquires hdev->lock.

Similarly for commit 6a5ad251b7cd ("Bluetooth: ISO: Fix possible circular locking dependency"). We retain the fix in iso_conn_ready to not acquire iso_conn_lock before lock_sock.

iso_conn_add shall return iso_conn with valid hcon. Make it so also when reusing an old CIS connection waiting for disconnect timeout (see __iso_sock_close where conn->hcon is set to NULL).

Trace with iso_conn_del after iso_chan_add in iso_connect_cis: =============================================================== iso_sock_create:771: sock 00000000be9b69b7 iso_sock_init:693: sk 000000004dff667e iso_sock_bind:827: sk 000000004dff667e 70:1a:b8:98:ff:a2 type 1 iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_connect:875: sk 000000004dff667e iso_connect_cis:353: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da hci_get_route:1199: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da hci_conn_add:1005: hci0 dst 28:3d:c2:4a:7e:da iso_conn_add:140: hcon 000000007b65d182 conn 00000000daf8625e __iso_chan_add:214: conn 00000000daf8625e iso_connect_cfm:1700: hcon 000000007b65d182 bdaddr 28:3d:c2:4a:7e:da status 12 iso_conn_del:187: hcon 000000007b65d182 conn 00000000daf8625e, err 16 iso_sock_clear_timer:117: sock 000000004dff667e state 3 iso_chan_del:153: sk 000000004dff667e, conn 00000000daf8625e, err 16 hci_conn_del:1151: hci0 hcon 000000007b65d182 handle 65535 hci_conn_unlink:1102: hci0: hcon 000000007b65d182 hci_chan_list_flush:2780: hcon 000000007b65d182 iso_sock_getsockopt:1376: sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getsockopt:1376: sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_shutdown:1434: sock 00000000be9b69b7, sk 000000004dff667e, how 1 __iso_sock_close:632: sk 000000004dff667e state 5 socket 00000000be9b69b7 BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 8000000006467067 P4D 8000000006467067 PUD 3f5f067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 RIP: 0010:__iso_sock_close (net/bluetooth/iso.c:664) bluetooth ===============================================================

Trace with iso_conn_del before iso_chan_add in iso_connect_cis: =============================================================== iso_connect_cis:356: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da ... iso_conn_add:140: hcon 0000000093bc551f conn 00000000768ae504 hci_dev_put:1487: hci0 orig refcnt 21 hci_event_packet:7607: hci0: e ---truncated---

CVSS v3
8.0
EG Score
8.0(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity80% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Bluetooth: ISO: fix iso_conn related locking and validity issues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d40ae85ee62e3666f45bc61864b22121346f88ef
generic

Bluetooth: ISO: fix iso_conn related locking and validity issues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88ad50f2b843a510bd7c922c0a4e2484aff9d645
generic

Bluetooth: ISO: fix iso_conn related locking and validity issues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e969bfed84c1f88dc722a678ee08488e86f0ec1a

Vendor Advisories for CVE-2023-54164(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.42—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)6.1.52-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 191 total refreshes for this CVE.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:14 UTCEPSS rescore
  3. 2026-09-19 21:50 UTCOSV refresh
  4. 2026-09-18 19:26 UTCEPSS rescore
  5. 2026-09-16 14:06 UTCEPSS rescore
  6. 2026-09-16 05:11 UTCEPSS rescore
  7. 2026-09-16 05:11 UTCEPSS rescore
  8. 2026-09-15 03:08 UTCEPSS rescore
  9. 2026-09-13 16:45 UTCEPSS rescore
  10. 2026-09-12 14:58 UTCEPSS rescore
  11. 2026-09-11 14:51 UTCEPSS rescore
  12. 2026-09-11 09:34 UTCEPSS rescore
  13. 2026-09-08 21:58 UTCEPSS rescore
  14. 2026-09-07 15:59 UTCEPSS rescore
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-05 15:26 UTCEPSS rescore
  17. 2026-09-04 13:58 UTCEPSS rescore
  18. 2026-09-04 05:04 UTCEPSS rescore
  19. 2026-09-02 14:10 UTCEPSS rescore
  20. 2026-09-01 13:52 UTCEPSS rescore
  21. 2026-09-01 04:36 UTCEPSS rescore
  22. 2026-09-01 01:04 UTCOSV refresh
  23. 2026-08-30 19:15 UTCEPSS rescore
  24. 2026-08-30 01:20 UTCEPSS rescore
  25. 2026-08-28 21:39 UTCEPSS rescore
Show 75 more
  1. 2026-08-27 14:23 UTCEPSS rescore
  2. 2026-08-26 14:44 UTCEPSS rescore
  3. 2026-08-25 13:47 UTCEPSS rescore
  4. 2026-08-23 00:17 UTCEPSS rescore
  5. 2026-08-23 00:17 UTCEPSS rescore
  6. 2026-08-21 23:47 UTCEPSS rescore
  7. 2026-08-20 22:53 UTCEPSS rescore
  8. 2026-08-19 17:02 UTCEPSS rescore
  9. 2026-08-18 13:46 UTCEPSS rescore
  10. 2026-08-16 14:54 UTCEPSS rescore
  11. 2026-08-16 02:12 UTCEPSS rescore
  12. 2026-08-15 01:28 UTCEPSS rescore
  13. 2026-08-15 01:20 UTCEG score recompute
  14. 2026-08-15 01:20 UTCGHSA enrichment
  15. 2026-08-13 21:58 UTCEPSS rescore
  16. 2026-08-12 13:49 UTCEPSS rescore
  17. 2026-08-11 13:40 UTCEPSS rescore
  18. 2026-08-10 23:58 UTCEPSS rescore
  19. 2026-08-09 22:24 UTCEG score recompute
  20. 2026-08-09 22:24 UTCGHSA enrichment
  21. 2026-08-09 13:44 UTCEPSS rescore
  22. 2026-08-08 16:35 UTCEPSS rescore
  23. 2026-08-08 04:36 UTCEG score recompute
  24. 2026-08-08 04:36 UTCGHSA enrichment
  25. 2026-08-07 16:25 UTCEPSS rescore
  26. 2026-08-06 13:45 UTCEPSS rescore
  27. 2026-08-06 06:47 UTCEG score recompute
  28. 2026-08-06 06:47 UTCGHSA enrichment
  29. 2026-08-05 19:15 UTCEPSS rescore
  30. 2026-08-05 19:15 UTCEPSS rescore
  31. 2026-08-05 10:12 UTCEG score recompute
  32. 2026-08-05 10:12 UTCGHSA enrichment
  33. 2026-08-04 11:27 UTCEG score recompute
  34. 2026-08-04 11:27 UTCGHSA enrichment
  35. 2026-08-04 10:36 UTCEPSS rescore
  36. 2026-08-04 10:22 UTCEG score recompute▲ 8.00
  37. 2026-08-04 10:22 UTCGHSA enrichment
  38. 2026-08-04 10:19 UTCMITRE cvelistV5CVSS v3 → 8 · severity → HIGH
  39. 2026-08-03 10:34 UTCEPSS rescore
  40. 2026-08-02 02:25 UTCEPSS rescore
  41. 2026-08-02 02:25 UTCEPSS rescore
  42. 2026-08-01 04:14 UTCEPSS rescore
  43. 2026-07-30 16:26 UTCEPSS rescore
  44. 2026-07-30 01:29 UTCEPSS rescore
  45. 2026-07-28 15:34 UTCEPSS rescore
  46. 2026-07-28 15:34 UTCEPSS rescore
  47. 2026-07-27 02:39 UTCOSV refresh
  48. 2026-07-26 14:53 UTCEPSS rescore
  49. 2026-07-25 14:16 UTCEPSS rescore
  50. 2026-07-24 14:16 UTCEPSS rescore
  51. 2026-07-23 14:16 UTCEPSS rescore
  52. 2026-07-23 02:30 UTCEG score recompute
  53. 2026-07-22 23:16 UTCEG score recompute
  54. 2026-07-22 14:07 UTCEPSS rescore
  55. 2026-07-22 14:07 UTCEPSS rescore
  56. 2026-07-21 15:23 UTCEPSS rescore
  57. 2026-07-20 17:06 UTCEPSS rescore
  58. 2026-07-19 14:30 UTCEPSS rescore
  59. 2026-07-19 14:29 UTCEPSS rescore
  60. 2026-07-19 02:27 UTCEPSS rescore
  61. 2026-07-19 02:27 UTCEPSS rescore
  62. 2026-07-18 10:03 UTCEPSS rescore
  63. 2026-07-18 10:03 UTCEPSS rescore
  64. 2026-07-16 17:01 UTCEPSS rescore
  65. 2026-07-15 16:56 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-15 01:59 UTCEPSS rescore
  68. 2026-07-13 22:28 UTCEPSS rescore
  69. 2026-07-13 22:28 UTCEPSS rescore
  70. 2026-07-13 06:11 UTCEPSS rescore
  71. 2026-07-12 05:45 UTCEPSS rescore
  72. 2026-07-12 05:45 UTCEPSS rescore
  73. 2026-07-11 08:26 UTCEPSS rescore
  74. 2026-07-09 21:17 UTCOSV refresh
  75. 2026-07-09 19:08 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2023-54164?
CVE-2023-54164 is a high vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix iso_conn related locking and validity issues sk->skstate indicates whether isopi(sk)->conn is valid. Operations that check/update skstate and access conn should hold locksock, otherwise they can race. The order…
When was CVE-2023-54164 disclosed?
CVE-2023-54164 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54164 actively exploited?
CVE-2023-54164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.8% of all scored CVEs.
What is the CVSS score of CVE-2023-54164?
CVE-2023-54164 has a CVSS v4.0 base score of 8.0 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54164, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54164

Explore →

Is Your Infrastructure Affected by CVE-2023-54164?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs