CVE-2023-52882
What it is
In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast majority of cases, now and then it causes instability. This leads to system crashes and other undefined behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can't observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.276
- Linux Kernel < 5.10.217
- Linux Kernel < 5.15.159
- Linux Kernel < 6.1.91
- Linux Kernel < 6.6.31
- Linux Kernel < 6.8.10
- Linux Kernel 6.9
- Debian Linux 10.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52882.md and follow it. Check whether this project is affected by CVE-2023-52882. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0b82eb134d2942ecc669e2ab2be3f0a58d79428a
- https://git.kernel.org/stable/c/70f64cb29014e4c4f1fabd3265feebd80590d069
- https://git.kernel.org/stable/c/7e91ed763dc07437777bd012af7a2bd4493731ff
- https://git.kernel.org/stable/c/9708e5081cfc4f085690294163389bcf82655f90
- https://git.kernel.org/stable/c/bfc78b4628497eb6df09a6b5bba9dd31616ee175
- https://git.kernel.org/stable/c/f1fa9a9816204ac4b118b2e613d3a7c981355019
- https://git.kernel.org/stable/c/fe11826ffa200e1a7a826e745163cb2f47875f66
- https://git.kernel.org/stable/c/0b82eb134d2942ecc669e2ab2be3f0a58d79428a
- https://git.kernel.org/stable/c/70f64cb29014e4c4f1fabd3265feebd80590d069
- https://git.kernel.org/stable/c/7e91ed763dc07437777bd012af7a2bd4493731ff
References
- https://git.kernel.org/stable/c/0b82eb134d2942ecc669e2ab2be3f0a58d79428a
- https://git.kernel.org/stable/c/70f64cb29014e4c4f1fabd3265feebd80590d069
- https://git.kernel.org/stable/c/7e91ed763dc07437777bd012af7a2bd4493731ff
- https://git.kernel.org/stable/c/9708e5081cfc4f085690294163389bcf82655f90
- https://git.kernel.org/stable/c/bfc78b4628497eb6df09a6b5bba9dd31616ee175
- https://git.kernel.org/stable/c/f1fa9a9816204ac4b118b2e613d3a7c981355019
- https://git.kernel.org/stable/c/fe11826ffa200e1a7a826e745163cb2f47875f66
- https://git.kernel.org/stable/c/0b82eb134d2942ecc669e2ab2be3f0a58d79428a
- https://git.kernel.org/stable/c/70f64cb29014e4c4f1fabd3265feebd80590d069
- https://git.kernel.org/stable/c/7e91ed763dc07437777bd012af7a2bd4493731ff
- https://git.kernel.org/stable/c/9708e5081cfc4f085690294163389bcf82655f90
- https://git.kernel.org/stable/c/bfc78b4628497eb6df09a6b5bba9dd31616ee175
- https://git.kernel.org/stable/c/f1fa9a9816204ac4b118b2e613d3a7c981355019
- https://git.kernel.org/stable/c/fe11826ffa200e1a7a826e745163cb2f47875f66
- https://lists.debian.org/debian-lts-announce/2024/06/msg00019.html
- https://security.netapp.com/advisory/ntap-20240912-0010/