LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9016: In blk_mq_tag_to_rq in blk-mq.c in the upstream kernel, there is a possible use after free due to a race co...

In blk_mq_tag_to_rq in blk-mq.c in the upstream kernel, there is a possible use after free due to a race condition when a request has been previously freed by blk_mq_complete_request. This could lead to local escalation of privilege. Product: Android. Versions: Android kernel. Android ID: A-63083046.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a kernel-level Android vulnerability where a race condition could let local code touch memory after it was freed. If exploitable on a vulnerable build, it could help an attacker with local access or a malicious app gain higher privileges. The public bundle does not provide CVSS, broad affected version detail, or evidence of active exploitation.

Executive priority

Handle through normal kernel patch governance, with higher priority for shared, unmanaged, or app-exposed Android fleets. It is not documented here as actively exploited, but kernel privilege escalation can materially increase the business impact of any initial compromise.

Technical view

CVE-2015-9016 is a possible use-after-free in upstream Linux blk-mq, specifically blk_mq_tag_to_rq in blk-mq.c, when a request was previously freed by blk_mq_complete_request. The reported impact is local escalation of privilege. The bundle names Android kernel as affected and cites an upstream Linux commit, Android bulletin, and Debian DSA-4187.

Likely exposure

Exposure is most relevant to Android kernel builds containing the vulnerable blk-mq code. The bundle also cites Debian DSA-4187, but does not include exact affected Debian package versions. Systems without local code execution paths are less exposed, because the stated impact is local privilege escalation, not remote compromise.

Exploitation context

The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The impact requires local execution context. Treat it as a privilege-escalation risk that can worsen another foothold, especially on devices where untrusted apps or users can run code.

Researcher notes

The evidence is sparse: no CVSS, CWE, detailed affected versions, or exploit status are supplied. The key technical anchor is a blk-mq use-after-free race involving request completion and tag-to-request lookup. Avoid over-scoping beyond Android kernel and cited vendor guidance without additional vendor-specific evidence.

Mitigation direction

  • Apply Android security updates covering the February 2018 bulletin guidance.
  • For Debian systems, review and apply updates from DSA-4187 if applicable.
  • Confirm kernel builds include the referenced upstream Linux fix commit.
  • Prioritize vendor-supported kernels over backporting manually.
  • Check vendor guidance where affected version details are unclear.

Validation and detection

  • Inventory Android devices and kernel build versions in scope.
  • Map kernel source or vendor changelogs to commit 0048b4837affd153897ed1222283492070027aa9.
  • Review Android February 2018 bulletin applicability for managed devices.
  • Review Debian DSA-4187 applicability for Debian-based assets.
  • Document any unsupported kernels needing replacement or isolation.
Prepared
Confidence
medium
Sources
5

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-2015-9016 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google Inc.AndroidAndroid kernelListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.