CVE-2024-57879: Bluetooth: iso: Always release hdev at the end of iso_listen_bis
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: iso: Always release hdev at the end of iso_listen_bis
Since hci_get_route holds the device before returning, the hdev
should be released with hci_dev_put at the end of iso_listen_bis
even if the function returns with an error.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Bluetooth issue involving incorrect cleanup of a held Bluetooth device object. The source describes a missing release path when an error occurs. Business impact is unclear because no CVSS, CWE, exploit details, or active exploitation evidence are provided.
Executive priority
Handle through normal kernel patch management unless your environment has broad Bluetooth-enabled Linux exposure. Escalate if a vendor rates it higher, publishes stronger impact detail, or exploitation evidence emerges.
Technical view
In the Bluetooth ISO code path, iso_listen_bis calls hci_get_route, which holds hdev before returning. The fix ensures hci_dev_put is called at the end of iso_listen_bis, including error returns. The likely class is resource or reference leak, but the source does not assign CWE or impact.
Likely exposure
Exposure appears limited to Linux kernels containing the affected Bluetooth ISO code. The bundle lists Linux as affected and references stable kernel fixes, but distro backport status and exact deployed package exposure must be verified with each vendor.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit availability, or weaponized details. Treat this as a kernel maintenance vulnerability until vendor advisories or telemetry indicate higher urgency.
Researcher notes
The public record is sparse. The core evidence is the upstream fix description: hci_get_route increments the device reference, and iso_listen_bis must release hdev on all exits. No CVSS, CWE, crashability, privilege boundary, or exploit preconditions are provided.
Mitigation direction
Update Linux kernels to builds that include the referenced stable fixes.
Check distribution vendor guidance for package availability and backports.
Prioritize review of systems where Bluetooth kernel support is enabled.
Track remediation by vendor package status, not only upstream version numbers.
Validation and detection
Compare fleet kernel versions against vendor advisories for CVE-2024-57879.
Confirm patched kernels include the referenced stable fix or documented backport.
Review Linux assets for Bluetooth support and relevant kernel versions.
After updating, verify hosts are running the remediated kernel.
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.
cve · low confidence lookup
CVE-2024-57879 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
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.
Jan 11, 2025, 15:05 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.