Use-After-Free Vulnerability in Linux Kernel - Debian Package

linux Updated 02 Oct 2025

Summary

26/02/2024
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2023-52468: In the Linux kernel, the following vulnerability has been resolved: class: fix use-after-free in class_register() The lock_class_key is still registered and can be found in lock_keys_hash hlist after subsys_private is fr... Affects linux versions < 6.6.15-1. Fixed in 6.6.15-1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is the core component of the Debian operating system, responsible for managing hardware and system resources. It provides essential services for all other parts of the system, including user applications. The kernel is designed to be robust and secure, but vulnerabilities can arise due to complex interactions within its code. This specific vulnerability affects the registration of lock classes, which can lead to instability and security risks if exploited.

Vulnerability Detail

In the Linux kernel, a use-after-free vulnerability has been identified in the class_register() function. This occurs when the lock_class_key remains registered and can be accessed after the associated memory has been freed. Specifically, if a task iterates over the lock_keys_hash after the memory has been released, it may lead to invalid memory access, potentially causing system crashes or exploitation by malicious actors. The issue arises during error handling when a driver fails to register due to a duplicate filename, leading to a KASAN (Kernel Address Sanitizer) report of invalid access.

How To Fix

Minimum fixed version

6.6.15-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch by updating the package as described above.

Conclusion

The use-after-free vulnerability in the Linux kernel poses significant risks to system stability and security. It is crucial for users of Debian systems to update their Linux packages to the patched version 6.6.15-1 or later to mitigate these risks. Regular monitoring and vulnerability management practices, such as using tools like Vulert, can help maintain system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a pointer after the memory it points to has been freed. This can lead to unpredictable behavior, crashes, or security exploits.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By uploading your manifest file, such as package-lock.json, you can check for vulnerabilities without needing to install any software.

Exploitation of this vulnerability could lead to system crashes, unauthorized access to system resources, or execution of arbitrary code, compromising the integrity and security of the system.

While this vulnerability has been identified in the Debian versions of the Linux kernel, similar vulnerabilities may exist in other distributions or versions of the kernel.

If immediate updates are not possible, consider isolating the affected system from critical networks and monitoring for any unusual activity until the patch can be applied.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.6.15-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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