CVE-2023-52629
What it is
In the Linux kernel, the following vulnerability has been resolved: sh: push-switch: Reorder cleanup operations to avoid use-after-free bug The original code puts flush_work() before timer_shutdown_sync() in switch_drv_remove(). Although we use flush_work() to stop the worker, it could be rescheduled in switch_timer(). As a result, a use-after-free bug can occur. The details are shown below: (cpu 0) | (cpu 1) switch_drv_remove() | flush_work() | ... | switch_timer // timer | schedule_work(&psw->work) timer_shutdown_sync() | ... | switch_work_handler // worker kfree(psw) // free | | psw->state = 0 // use This patch puts timer_shutdown_sync() before flush_work() to mitigate the bugs. As a result, the worker and timer will be stopped safely before the deallocate operations.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering, 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: 8.4 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.5.4
Attack profile CVSS 3.1 · 8.4
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-52629.md and follow it. Check whether this project is affected by CVE-2023-52629. 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/246f80a0b17f8f582b2c0996db02998239057c65
- https://git.kernel.org/stable/c/610dbd8ac271aa36080aac50b928d700ee3fe4de
- https://git.kernel.org/stable/c/246f80a0b17f8f582b2c0996db02998239057c65
- https://git.kernel.org/stable/c/610dbd8ac271aa36080aac50b928d700ee3fe4de
References
- https://git.kernel.org/stable/c/246f80a0b17f8f582b2c0996db02998239057c65
- https://git.kernel.org/stable/c/610dbd8ac271aa36080aac50b928d700ee3fe4de
- https://git.kernel.org/stable/c/ff635d1f143b55fa005e9e43b16e6d8f677e90a5
- https://git.kernel.org/stable/c/246f80a0b17f8f582b2c0996db02998239057c65
- https://git.kernel.org/stable/c/610dbd8ac271aa36080aac50b928d700ee3fe4de