Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-28464 is a high-severity Double Free (CWE-415) vulnerability in Linux Kernel. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32142
Vulnerability Data
hci_conn_cleanup in net/bluetooth/hci_conn.c in the Linux kernel through 6.2.9 has a use-after-free (observed in hci_conn_hash_flush) because of calls to hci_dev_put and hci_conn_put. There is a double free that may lead to privilege escalation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development can detect double-free conditions before release.
Training developers on secure memory management practices (proper error handling around free(), avoiding double-free in cleanup paths) reduces a minority of CWE-415 instances, but the bug is subtle, often arises from race conditions and complex error paths, and even well-trained developers introduce it — consistent with the A.8.28 -> CWE-79 and A.6.3 -> CWE-598 partial pattern.
Secure coding standards directly address proper use of free() and similar functions.
A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a double-free defect in delivered code is reduced the way those practices reduce it; the same reasoning the owner applied to A.8.30 -> CWE-134 (format string) at `partial` applies here, and the clause carries a declared ceiling of `partial` on this verb.
A.8.8's reach is DISCLOSURE — it finds double-free instances only where they appear as published advisories in third-party components (multiple CVEs exist for CWE-415), but the majority of double-free bugs in custom first-party code are never published and so are outside this control's view, matching the same disclosure-bound reasoning that graded A.8.8 finds CWE-89 = partial.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
Oracle Linux 8 (1 partial rule)
- V-248590 OL 8 must clear the page allocator to prevent use-after-free attacks. blocks CWE-415