CVE-2024-26889: Bluetooth: hci_core: Fix possible buffer overflow
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Fix possible buffer overflow
struct hci_dev_info has a fixed size name[8] field so in the event that
hdev->name is bigger than that strcpy would attempt to write past its
size, so this fixes this problem by switching to use strscpy.
Security readout for executives and security teams
Plain-English summary
CVE-2024-26889 is a Linux kernel Bluetooth flaw where an oversized device name could overflow a fixed eight-byte field. The published impact is denial of service, not data theft or privilege escalation. It requires local low-privileged access, so urgency depends on whether exposed systems permit local users and run affected kernels.
Executive priority
Treat this as a routine but real availability risk. Patch during the normal kernel maintenance cycle, faster for shared Linux hosts, managed appliances, or environments where untrusted local users can run code. It does not currently warrant emergency response based on the supplied evidence.
Technical view
The Linux Bluetooth hci_core code copied hdev->name into struct hci_dev_info name[8] using strcpy. The fix replaces that unsafe copy with strscpy. The CVE maps to CWE-120 and CVSS 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most plausible on Linux systems running affected kernel versions or downstream builds that include the vulnerable Bluetooth code. Systems without local untrusted users, without Bluetooth support, or already updated by their distribution have lower practical exposure. The source bundle does not provide a complete downstream product matrix.
Exploitation context
The CVE record does not report active exploitation, and KEV status is false. The stated attacker position is local, low privilege. Public sources provided describe the code fix and vendor advisories, but do not provide evidence of remote exploitation or a public weaponized exploit.
Researcher notes
The key issue is bounded copy correctness in hci_dev_info population. Source version data is commit and release based, so distro backports need vendor confirmation. Avoid assuming exploitability beyond local denial of service unless additional evidence emerges from a vendor or KEV source.
Mitigation direction
Apply the relevant Linux kernel or distribution security update.
Check Debian LTS and vendor advisories for fixed package versions.
For appliances, follow the vendor advisory before changing kernels manually.
Reduce local untrusted access on affected hosts until patched.
Disable unused Bluetooth functionality where operationally acceptable.
Validation and detection
Inventory running kernel versions across Linux assets.
Compare kernels against distribution and vendor advisory status.
Confirm Bluetooth support is present and enabled on affected hosts.
Verify patched kernel packages are installed after maintenance.
Prioritize multi-user systems and devices with local shell access.
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.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.