CVE-2021-47318
Last modified
CVE-2021-47318 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.23% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 5.13.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2021-47318?
How severe is CVE-2021-47318?
How do I fix CVE-2021-47318?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2021
- CVE-2021-47312In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47313In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2021-47314In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47315In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47316In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47317In the Linux kernel, the following vulnerability has been re…3.3
- CVE-2021-47319In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47320In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2021-47321In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47322In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2021-47323In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2021-47324In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2021-47318?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
