CVE-2025-63895: An issue in the Bluetooth firmware of JXL 9 Inch Car Android Double Din Player Android v12.0 allows attacke...
An issue in the Bluetooth firmware of JXL 9 Inch Car Android Double Din Player Android v12.0 allows attackers to cause a Denial of Service (DoS) via sending a crafted Link Manager Protocol (LMP) packet.
Security readout for executives and security teams
Plain-English summary
This CVE describes a Bluetooth firmware flaw in a JXL 9 Inch Car Android Double Din Player running Android v12.0. A malformed Bluetooth Link Manager Protocol packet can reportedly crash or disrupt the device, affecting availability rather than data confidentiality or integrity.
Executive priority
Prioritize identification over broad emergency action. The business risk is localized service disruption to affected infotainment devices, but patch status and exact product identifiers are incomplete, so procurement and fleet teams should confirm exposure quickly.
Technical view
The CVE record assigns CVSS 3.1 score 7.5 with high availability impact and no listed privileges or user interaction. The stated weakness is CWE-404. Public metadata does not provide CPEs, a vendor advisory, affected firmware ranges, or a confirmed patch.
Likely exposure
Exposure appears limited to environments using the named JXL Android v12.0 aftermarket car infotainment unit. The official affected product fields are marked n/a, so asset confirmation must rely on device model, firmware, procurement records, or the cited research reference.
Exploitation context
CISA KEV status is false, and the provided sources do not claim active exploitation. The record states exploitation involves a crafted Bluetooth LMP packet causing denial of service; no exploit maturity, range assumptions, or public weaponization details are established in the bundle.
Researcher notes
The evidence base is thin: official affected fields are n/a, no CPEs are listed, and only one public GitHub reference is provided. Validate claims in a controlled lab and avoid extrapolating to other Android head units or Bluetooth chipsets.
Mitigation direction
Check JXL, reseller, or firmware supplier guidance for updates or replacement advice.
Treat Bluetooth disablement as temporary exposure reduction where operationally acceptable.
Avoid pairing the unit with unknown or untrusted Bluetooth devices.
Replace affected units in high-availability or safety-sensitive deployments if vendor guidance remains unavailable.
Track the CVE and cited repository for corrected firmware or vendor clarification.
Validation and detection
Inventory vehicles or test benches using the named JXL Android v12.0 head unit.
Confirm model and firmware through device settings, labels, or procurement records.
Check whether Bluetooth is enabled and required for business operations.
Review incident logs for unexpected infotainment resets or Bluetooth instability.
Do not test malformed Bluetooth traffic on production vehicles.
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-404: 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-404 · source CWE mapping
Improper Resource Shutdown or Release
Improper Resource Shutdown or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.