LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47375: blktrace: Fix uaf in blk_trace access after removing by sysfs

In the Linux kernel, the following vulnerability has been resolved: blktrace: Fix uaf in blk_trace access after removing by sysfs There is an use-after-free problem triggered by following process: P1(sda) P2(sdb) echo 0 > /sys/block/sdb/trace/enable blk_trace_remove_queue synchronize_rcu blk_trace_free relay_close rcu_read_lock __blk_add_trace trace_note_tsk (Iterate running_trace_list) relay_close_buf relay_destroy_buf kfree(buf) trace_note(sdb's bt) relay_reserve buf->offset <- nullptr deference (use-after-free) !!! rcu_read_unlock [ 502.714379] BUG: kernel NULL pointer dereference, address: 0000000000000010 [ 502.715260] #PF: supervisor read access in kernel mode [ 502.715903] #PF: error_code(0x0000) - not-present page [ 502.716546] PGD 103984067 P4D 103984067 PUD 17592b067 PMD 0 [ 502.717252] Oops: 0000 [#1] SMP [ 502.720308] RIP: 0010:trace_note.isra.0+0x86/0x360 [ 502.732872] Call Trace: [ 502.733193] __blk_add_trace.cold+0x137/0x1a3 [ 502.733734] blk_add_trace_rq+0x7b/0xd0 [ 502.734207] blk_add_trace_rq_issue+0x54/0xa0 [ 502.734755] blk_mq_start_request+0xde/0x1b0 [ 502.735287] scsi_queue_rq+0x528/0x1140 ... [ 502.742704] sg_new_write.isra.0+0x16e/0x3e0 [ 502.747501] sg_ioctl+0x466/0x1100 Reproduce method: ioctl(/dev/sda, BLKTRACESETUP, blk_user_trace_setup[buf_size=127]) ioctl(/dev/sda, BLKTRACESTART) ioctl(/dev/sdb, BLKTRACESETUP, blk_user_trace_setup[buf_size=127]) ioctl(/dev/sdb, BLKTRACESTART) echo 0 > /sys/block/sdb/trace/enable & // Add delay(mdelay/msleep) before kernel enters blk_trace_free() ioctl$SG_IO(/dev/sda, SG_IO, ...) // Enters trace_note_tsk() after blk_trace_free() returned // Use mdelay in rcu region rather than msleep(which may schedule out) Remove blk_trace from running_list before calling blk_trace_free() by sysfs if blk_trace is at Blktrace_running state.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
  • Review shared or multi-tenant Linux hosts first.
  • Avoid enabling blktrace unless operationally required.

Validation and detection

  • Inventory Linux kernel versions across affected server and workstation fleets.
  • Confirm vendor kernel changelogs mention CVE-2021-47375 or the stable fix commits.
  • Check whether blktrace and /sys/block/*/trace are available on sensitive systems.
  • Prioritize validation on multi-user, CI, build, and shared compute hosts.
Prepared
Confidence
high
Sources
10

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47375 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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.

1CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2021-47375Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199, c71a896154119f4ca9e89d6078f5f63ad60ef199unaffected
LinuxLinux2.6.30, 0, 4.4.286, 4.9.285, 4.14.249, 4.19.209, 5.4.150, 5.10.70, 5.14.9, 5.15affected
Weakness

CWE details

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.