Security readout for executives and security teams
Plain-English summary
This is a local Android/Linux kernel driver issue in Qualcomm MSM-related TSC broadcast code. A malicious app could crash the device or kernel component, causing denial of service. The public record also mentions possible unspecified impact, but does not provide enough evidence to rate it beyond that.
Executive priority
Treat this as a legacy mobile platform risk. It is not supported by evidence of active exploitation, but affected unsupported Android/MSM devices may be difficult to patch and should be prioritized for firmware validation or replacement.
Technical view
CVE-2015-0573 affects drivers/media/platform/msm/broadcast/tsc.c in the TSC driver for Linux kernel 3.x used in QuIC Android contributions for MSM devices. The flaw is an invalid pointer dereference reachable through a TSC_GET_CARD_STATUS ioctl from a crafted application.
Likely exposure
Exposure is most likely on older Android devices or downstream kernel builds using Qualcomm MSM Linux 3.x code with the affected TSC driver present. The source bundle does not identify exact OEM models, maintained branches, or package versions.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. The described attacker position is local application execution, not unauthenticated remote access. Expected confirmed impact is denial of service; other impact is not specified.
Researcher notes
The public data is sparse: no CVSS, CWE, exact product matrix, or exploit confirmation is supplied. Analysis should stay tied to Qualcomm MSM Linux 3.x derivatives and the TSC driver path unless vendor evidence expands scope.
Mitigation direction
- Identify Android/MSM devices using affected Linux 3.x TSC driver code.
- Apply OEM or vendor firmware updates containing the referenced Qualcomm/CodeAurora fix.
- Check vendor guidance before disabling or removing TSC driver functionality.
- Reduce sideloading and untrusted app installation on exposed legacy devices.
- Retire unsupported devices that cannot receive kernel or firmware fixes.
Validation and detection
- Inventory device models, firmware versions, and kernel branches in mobile fleets.
- Confirm whether the TSC driver source is present in deployed kernel builds.
- Compare vendor kernel source or build notes against the referenced fix commit.
- Review OEM security bulletins for CVE-2015-0573 coverage.
- Check device crash telemetry for repeated kernel driver faults.
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-2015-0573 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://us.codeaurora.org/cgit/quic/la//kernel/msm-3.10/commit/?id=e20f20aaed6b6d2fd1667bad9be9ef35103a51dfCVE reference · x_refsource_CONFIRM
- https://www.codeaurora.org/issues-tsc-tspp2-and-buspm-drivers-cve-2015-0573-cve-2016-2441-cve-2016-2442CVE reference · x_refsource_CONFIRM
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.
