Security readout for executives and security teams
Plain-English summary
A Linux Bluetooth kernel race can access memory after an SCO socket has been freed. This may crash or corrupt the system; the CVSS assessment also allows potential confidentiality, integrity, and availability impact. The supplied evidence demonstrates the defect with a KASAN-triggering proof of concept, but does not establish real-world compromise.
Executive priority
Treat this as a high-priority kernel maintenance issue on Bluetooth-enabled or multi-user Linux systems. Accelerate normal patching where SCO functionality is exposed to less-trusted users. Emergency response is not supported by the supplied evidence because active exploitation is unconfirmed and the stated attack vector is adjacent rather than internet-remote.
Technical view
A delayed timeout worker scheduled during SCO socket closure can run after sock_put deallocates the socket. sco_sock_timeout then calls sock_hold on the freed object, producing a slab use-after-free. The supplied CVSS v3.1 score is 8.0, with adjacent access, low privileges, no user interaction, and potentially high impact.
Likely exposure
Exposure centers on Linux systems running affected kernels where Bluetooth SCO functionality is available. The CVSS vector indicates adjacent access and low privileges, which constrain reachability compared with an unauthenticated remote flaw. The bundle lists affected versions, but its version data is ambiguous; confirm status through the relevant Linux distributor or appliance vendor.
Exploitation context
The source describes a proof of concept that triggered a KASAN use-after-free report. CVE-2024-27398 is not marked as CISA KEV in the supplied bundle, and no cited evidence establishes active exploitation. The bundle also does not demonstrate whether practical outcomes extend beyond memory corruption or denial of service.
Researcher notes
The race occurs between sco_sock_release freeing the socket and delayed timeout work dereferencing it. Multiple stable-kernel commits are cited as fixes. The supplied affected-version representation contains commit identifiers and releases without clear range semantics, so package-level exposure needs vendor confirmation. No CWE was supplied, although the described defect is explicitly a use-after-free.
Mitigation direction
Install a vendor-supported kernel update containing the cited SCO socket timeout fix.
Prioritize Bluetooth-capable systems where untrusted low-privilege users can access SCO functionality.
If patching is delayed, restrict unnecessary Bluetooth access or disable Bluetooth where operationally acceptable.
Reboot into the updated kernel and verify the vulnerable kernel is no longer running.
Validation and detection
Inventory Linux systems with Bluetooth enabled and record running kernel and distributor package versions.
Compare packages with distributor advisories and cited stable-kernel fixes; do not rely solely on upstream version strings.
Confirm the deployed kernel contains the SCO socket timeout fix after maintenance.
Review kernel diagnostics for use-after-free reports referencing sco_sock_timeout.
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-27398 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.
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.