Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in block tracing. A local actor could trigger a race where tracing data is freed while still being used, potentially crashing the kernel or exposing memory. The source bundle does not show active exploitation or a standalone vendor advisory beyond kernel stable fixes.
Executive priority
Treat as a moderate kernel maintenance issue. It is not documented as actively exploited, but kernel memory safety bugs matter on shared Linux systems. Prioritize routine patching, with faster action for multi-user or high-value hosts.
Technical view
CVE-2021-47375 is a CWE-416 use-after-free in Linux blktrace. Disabling tracing through sysfs can free blk_trace resources while __blk_add_trace still iterates running_trace_list and reaches relay_reserve through stale state. The stated fix removes blk_trace from the running list before blk_trace_free when tracing is running.
Likely exposure
Exposure is mainly Linux systems running affected kernel versions with blktrace/block tracing available. Risk is higher on multi-user systems, shared compute, and hosts where local users or workloads can reach block device tracing paths. Practical reachability may depend on device and sysfs permissions.
Exploitation context
The provided CVSS is 6.2 with local attack vector, low complexity, no user interaction, and high confidentiality impact. KEV is false, and the bundle provides no evidence of exploitation in the wild. The included reproduction detail indicates local kernel interaction, not remote exploitation.
Researcher notes
The evidence supports a race in blktrace teardown versus trace emission. The source describes stale blk_trace access after sysfs removal and a fix ordering change around running_trace_list and blk_trace_free. Do not assume remote reachability or weaponized exploit availability from the provided sources.
Mitigation direction
Update to a kernel build containing the referenced stable fixes.
Check distribution advisories for backported CVE-2021-47375 fixes.
Restrict local access to block devices and tracing interfaces where possible.
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-416: 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-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.