Security readout for executives and security teams
Plain-English summary
CVE-2017-13273 is an Android kernel flaw in xt_qtaguid.c. A local attacker could exploit a race condition to gain higher privileges. No user interaction is required, but the sources do not show remote exploitation or active exploitation.
Executive priority
Treat this as a patch governance issue for legacy Android fleets. It enables local privilege escalation, but the supplied evidence does not support emergency active-exploitation handling.
Technical view
The issue is insufficient locking in Android kernel xt_qtaguid.c, creating a race condition that can lead to local privilege escalation. The CVE record names Android kernel as affected and provides no CVSS score, CWE, exploit details, or affected device matrix.
Likely exposure
Exposure is most likely on Android devices running vendor kernel builds that had not incorporated the February 2018 Android security bulletin fixes. Exact OEM/device impact is not specified in the supplied sources.
Exploitation context
The source bundle says exploitation requires local access and no additional execution privileges or user interaction. There is no KEV listing and no cited evidence of active exploitation.
Researcher notes
Public details are sparse. The key confirmed facts are the Android kernel component, race condition, local privilege escalation impact, no user interaction requirement, and Android bug ID A-65853158.
Mitigation direction
- Apply vendor Android security updates tied to the February 2018 bulletin or later.
- Check OEM advisories for device-specific kernel update availability and patch levels.
- Prioritize managed, shared, or high-risk Android devices if patch status is uncertain.
- Retire or isolate devices that cannot receive supported vendor kernel updates.
Validation and detection
- Inventory Android devices and record OS version, vendor build, and security patch level.
- Confirm whether each device includes the February 2018 Android security bulletin fixes.
- Review MDM or EMM compliance reports for outdated Android security patch levels.
- For unsupported devices, document compensating controls and replacement timelines.
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-2017-13273 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://source.android.com/security/bulletin/2018-02-01CVE 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.