# CVE-2023-52629: sh: push-switch: Reorder cleanup operations to avoid use-after-free bug

> A use-after-free vulnerability in the Linux kernel's sh: push-switch driver allows attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Mar 2024
- **Updated:** 3 Oct 2026
- **Also known as:** BELL-CVE-2023-52629, DEBIAN-CVE-2023-52629, GHSA-384v-9gx5-rmx4, ROOT-OS-DEBIAN-11-CVE-2023-52629, ROOT-OS-DEBIAN-12-CVE-2023-52629, UBUNTU-CVE-2023-52629

## What is CVE-2023-52629?

CVE-2023-52629 is a high-severity use after free vulnerability in Linux kernel, published on 29 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2023-52629?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52629?

Apply the vendor's patch.

## Is CVE-2023-52629 being exploited?

There is no known exploitation of CVE-2023-52629 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52629 and fix it if it is affected.

What it is: CVE-2023-52629 is a high-severity use after free vulnerability in Linux kernel, published on 29 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52629 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52629/ (Markdown: https://insights.sbomify.com/CVE-2023-52629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52629
- OSV: https://osv.dev/vulnerability/CVE-2023-52629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52629/
Summaries are generated and may contain mistakes; the official description above is the record.