LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10689: blktrace (aka Block IO Tracing) 1.2.0, as used with the Linux kernel and Android, has a buffer overflow in...

blktrace (aka Block IO Tracing) 1.2.0, as used with the Linux kernel and Android, has a buffer overflow in the dev_map_read function in btt/devmap.c because the device and devno arrays are too small, as demonstrated by an invalid free when using the btt program with a crafted file.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-10689 is a buffer overflow in blktrace’s btt utility. A crafted file can trigger memory corruption when btt reads device mapping data. The source bundle does not show active exploitation or a CVSS score, so urgency depends on whether the tool is installed and used with untrusted trace data.

Executive priority

Treat this as a targeted hygiene issue, not a broad emergency based on the supplied evidence. Prioritize patching systems where blktrace is installed and trace files may come from untrusted sources.

Technical view

The flaw is in dev_map_read in btt/devmap.c in blktrace 1.2.0. The CVE states the device and devno arrays are too small, demonstrated by an invalid free when btt processes a crafted file. Public references include an upstream commit and Red Hat and Gentoo advisories.

Likely exposure

Exposure is most likely on Linux or Android-related environments where blktrace/btt is installed and users process external or untrusted trace files. This is not described as a network-facing service vulnerability in the provided sources.

Exploitation context

The source bundle does not identify active exploitation, and KEV is false. Public technical references and vendor advisories exist, but the provided evidence does not establish exploit maturity beyond crafted-file triggering of the bug.

Researcher notes

Do not assume kernel-level remote exposure from the CVE text alone. The described trigger is btt processing a crafted file. Severity, CWE, and CVSS are absent in the provided record, so validation should focus on package presence, fixed versions, and input handling practices.

Mitigation direction

  • Update blktrace packages using applicable vendor advisories.
  • Apply the upstream fix corresponding to commit d61ff409cb4dda31386373d706ea0cfb1aaac5b7 where relevant.
  • Avoid processing untrusted blktrace or btt input files.
  • Limit blktrace/btt access to trusted administrative users.
  • Check OS vendor guidance for supported fixed package versions.

Validation and detection

  • Inventory systems for installed blktrace and btt binaries.
  • Check package versions against Red Hat, Gentoo, or relevant vendor advisories.
  • Confirm whether teams process trace files from external sources.
  • Review build manifests for bundled blktrace 1.2.0 components.
  • Verify patched systems include the upstream dev_map_read fix.
Prepared
Confidence
medium
Sources
6

Public sources used

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-2018-10689 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
5Source 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
n/an/an/aListed
Weakness

CWE details

No CWE listed

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