Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth flaw can leave software pointing to memory that has already been freed when L2CAP socket creation fails. A low-privileged local user may be able to trigger memory corruption, potentially affecting system confidentiality, integrity, and availability. The supplied CVSS score is 7.8.
Executive priority
Prioritize normal high-severity patching, accelerating internet-facing, shared, kiosk, or multi-user Linux systems where untrusted users obtain local access. This is not evidenced as actively exploited, but kernel memory corruption and the stated confidentiality, integrity, and availability impacts justify timely remediation.
Technical view
bt_sock_alloc() allocates a kernel socket object and attaches it to a sock structure. If l2cap_sock_alloc() later fails, it frees that object without clearing the attached pointer. Subsequent code may dereference the stale pointer, creating a CWE-416 use-after-free condition.
Likely exposure
Exposure is most relevant to systems running an affected Linux kernel with Bluetooth L2CAP functionality reachable by low-privileged local users. The supplied version data is ambiguous and includes commit identifiers, so determine exposure using distribution package advisories and fix inclusion rather than version strings alone.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high impact. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Practical exploitability is therefore not established here.
Researcher notes
The flaw occurs on an error path in l2cap_sock_create() and concerns ownership consistency between the sock structure and its freed sk object. The references show multiple stable-branch fixes. The bundle does not establish trigger reliability, exploit primitives, affected configurations, or exploitation in the wild.
Mitigation direction
- Install a vendor-supported kernel package containing the applicable Linux stable fix.
- Review the referenced Debian advisories when operating affected Debian LTS systems.
- Reboot into the updated kernel after package installation.
- If updates are delayed, restrict untrusted local access and review vendor-recommended temporary mitigations.
Validation and detection
- Record the running kernel and distribution package versions across Linux assets.
- Confirm the installed package includes the applicable referenced stable-kernel commit.
- Verify systems rebooted into the corrected kernel rather than retaining the vulnerable kernel.
- Check distribution security advisories for backported fixes and affected-package status.
- Monitor vendor guidance because the supplied affected-version list is not sufficiently precise alone.
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.
CWE-416: 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.
Open ATT&CK lookupCVE-2024-56605 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f6ad641646b67f29c7578dcd6c25813c7dcbf51eCVE reference, Linux
- https://git.kernel.org/stable/c/daa13175a6dea312a76099066cb4cbd4fc959a84CVE reference, Linux
- https://git.kernel.org/stable/c/a8677028dd5123e5e525b8195483994d87123de4CVE reference, Linux
- https://git.kernel.org/stable/c/bb2f2342a6ddf7c04f9aefbbfe86104cd138e629CVE reference, Linux
- https://git.kernel.org/stable/c/8ad09ddc63ace3950ac43db6fbfe25b40f589dd6CVE reference, Linux
- https://git.kernel.org/stable/c/61686abc2f3c2c67822aa23ce6f160467ec83d35CVE reference, Linux
- https://git.kernel.org/stable/c/7c4f78cdb8e7501e9f92d291a7d956591bf73be9CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.htmlCVE reference, CVE
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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.