CVE-2023-52629: linux-libc-dev - Reorder cleanup operations to avoid use-after-free bug

linux Updated 02 Oct 2025

Summary

29/03/2024
No i
Unrated
Not published

CVE-2023-52629: 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_r... Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

linux-libc-dev is a package that provides the Linux kernel headers for use in userspace. It allows developers to compile and build applications that interact with the Linux kernel. The linux-libc-dev package is vulnerable to a use-after-free bug that can occur when the flush_work() function is called before timer_shutdown_sync() in the switch_drv_remove() function. This vulnerability can lead to a variety of issues, including crashes, privilege escalation, and potentially remote code execution.

Vulnerability Detail

The vulnerability in linux-libc-dev arises from the incorrect order of cleanup operations in the switch_drv_remove() function. The original code places flush_work() before timer_shutdown_sync(), which can result in the worker being rescheduled in switch_timer() after being stopped by flush_work(). This can lead to a use-after-free bug, where the worker and timer are accessed after they have been deallocated. An attacker could potentially exploit this vulnerability to execute arbitrary code or crash the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the patch provided by the Linux kernel developers.

Conclusion

The linux-libc-dev package is vulnerable to a use-after-free bug due to the incorrect order of cleanup operations. This vulnerability can have serious consequences, including crashes, privilege escalation, and potential remote code execution. Users of linux-libc-dev should update to the patched version as soon as possible to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

linux-libc-dev is a package that provides the Linux kernel headers for use in userspace. It allows developers to compile and build applications that interact with the Linux kernel.

A use-after-free bug occurs when a program continues to use a memory address after it has been deallocated. This can lead to crashes, privilege escalation, and potentially remote code execution.

An attacker could exploit this vulnerability by triggering the use-after-free bug, potentially leading to the execution of arbitrary code or crashing the system.

There is no known workaround for this vulnerability. It is recommended to apply the patch provided by the Linux kernel developers.

To update linux-libc-dev to the patched version, users should follow the instructions provided by their Linux distribution or package manager. It is important to regularly update software to ensure the latest security patches are applied.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback