CVE-2021-47318: arch_topology: Avoid use-after-free for scale_freq_data
In the Linux kernel, the following vulnerability has been resolved:
arch_topology: Avoid use-after-free for scale_freq_data
Currently topology_scale_freq_tick() (which gets called from
scheduler_tick()) may end up using a pointer to "struct
scale_freq_data", which was previously cleared by
topology_clear_scale_freq_source(), as there is no protection in place
here. The users of topology_clear_scale_freq_source() though needs a
guarantee that the previously cleared scale_freq_data isn't used
anymore, so they can free the related resources.
Since topology_scale_freq_tick() is called from scheduler tick, we don't
want to add locking in there. Use the RCU update mechanism instead
(which is already used by the scheduler's utilization update path) to
guarantee race free updates here.
synchronize_rcu() makes sure that all RCU critical sections that started
before it is called, will finish before it returns. And so the callers
of topology_clear_scale_freq_source() don't need to worry about their
callback getting called anymore.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47318 is a Linux kernel use-after-free bug in CPU frequency topology handling. A scheduler tick could use data after another path cleared it. The public record does not provide CVSS, proven impact, or active exploitation evidence, so urgency depends on whether affected 5.13-era kernels remain in use.
Executive priority
Treat this as a kernel hygiene issue requiring inventory-driven remediation, not an emergency exploitation event based on current sources. Prioritize systems where kernel compromise or instability would have high operational impact.
Technical view
The flaw is in arch_topology. topology_scale_freq_tick(), called from scheduler_tick(), could reference struct scale_freq_data after topology_clear_scale_freq_source() cleared it. The fix uses RCU synchronization so callers can safely free related resources after prior readers complete, avoiding race-prone pointer reuse.
Likely exposure
Exposure appears limited to Linux kernel versions identified in the CVE bundle, including 5.13-era releases. Organizations with unmanaged servers, appliances, embedded Linux, or custom kernel builds should verify exact kernel versions and whether the referenced stable fixes are present.
Exploitation context
The provided sources do not show public exploitation, KEV listing, exploit code, or real-world abuse. The issue is a kernel memory-safety race, but the bundle does not state whether it enables privilege escalation, denial of service, or only instability.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or explicit impact is provided. The clearest technical signal is the upstream fix description: replacing unprotected cleared-pointer reuse with RCU synchronization around scale_freq_data readers and clearers.
Mitigation direction
Check vendor kernel advisories for your distribution or device platform.
Update affected Linux kernels to a release containing the referenced stable fixes.
Prioritize internet-facing, multi-user, and untrusted-workload Linux systems.
Plan remediation for embedded or appliance kernels that may lag upstream fixes.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, appliances, and images.
Compare deployed kernels against vendor advisories for CVE-2021-47318.
Confirm whether the referenced arch_topology RCU fix is included in custom kernels.
Review change-management records for kernel updates after the relevant stable commits.
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-2021-47318 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.