Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth connection cleanup flaw can allow delayed work to be rescheduled while its owning object is being freed. This unsafe lifecycle may lead to serious memory corruption. The supplied CVSS score is 8.8, reflecting potentially high confidentiality, integrity, and availability impact from an adjacent attacker.
Executive priority
Assign high priority to identifying and updating exposed Bluetooth-capable Linux endpoints, especially portable or publicly accessible systems. Use vendor package status rather than raw version numbers alone because downstream kernels commonly backport fixes. No supplied evidence supports declaring an active incident solely from this CVE.
Technical view
The Bluetooth hci_conn cleanup path used cancel_delayed_work_sync, which cancels current work but does not prevent new submissions. The resolution uses disable_delayed_work_sync so work cannot be resubmitted while the containing object is being freed. The supplied sources do not identify a CWE or document the exact corruption outcome.
Likely exposure
Exposure is most relevant to systems running affected Linux builds with Bluetooth available to nearby devices. The supplied version metadata lists several versions and commit identifiers but does not clearly express complete affected or fixed ranges. Distribution-specific kernel advisories and backport status are therefore necessary for an accurate inventory decision.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no provided source reports active exploitation or a public exploit. The CVSS vector describes adjacent-network reachability, low complexity, no privileges, and no user interaction. Treat those characteristics as severity indicators, not proof of practical exploitation.
Researcher notes
The core issue is incomplete delayed-work shutdown during hci_conn object destruction. The fix prevents resubmission as well as synchronizing cancellation. Source evidence does not establish a specific trigger, resulting memory-corruption primitive, affected-range boundaries, public proof of concept, or exploitation in the wild; further vendor and code-level validation is required.
Mitigation direction
- Apply vendor-supported kernel updates containing the Bluetooth hci_conn fix.
- Confirm distribution kernels include either listed stable commit or an equivalent backport.
- If updates are unavailable, consult vendor guidance and consider disabling unnecessary Bluetooth functionality.
- Prioritize Bluetooth-capable systems used in public or otherwise untrusted physical environments.
Validation and detection
- Inventory deployed kernel builds and compare them with distribution-specific CVE advisories.
- Verify package changelogs or source provenance for the listed fix commits or equivalent backports.
- Identify systems where Bluetooth is enabled and reachable by nearby untrusted devices.
- Review Bluetooth-related kernel crashes or memory-safety alerts, recognizing that clean logs do not prove safety.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-56591 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c55a4c5a04bae40dcdc1e1c19d8eb79a06fb3397CVE reference, Linux
- https://git.kernel.org/stable/c/2b0f2fc9ed62e73c95df1fa8ed2ba3dac54699dfCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.