CVE-2024-35861: Vulnerability in linux-libc-dev package - Potential UAF in cifs_signal_cifsd_for_reconnect()

linux Updated 02 Oct 2025

Summary

19/05/2024
No i
High
7.8

CVE-2024-35861: In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential UAF in cifs_signal_cifsd_for_reconnect() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF. 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 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-libc-dev package is a development package that provides the necessary header files and libraries for compiling programs that use the Linux kernel interfaces. It is an essential component for building and linking applications on Linux systems. The package is widely used by developers and is included in various Linux distributions. However, the linux-libc-dev package is vulnerable to a potential Use-After-Free (UAF) vulnerability in the cifs_signal_cifsd_for_reconnect() function.

Vulnerability Detail

The vulnerability in the linux-libc-dev package arises from a potential Use-After-Free (UAF) issue in the cifs_signal_cifsd_for_reconnect() function. This vulnerability can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with kernel privileges. The vulnerability occurs when sessions that are being torn down are not properly skipped, leading to a UAF condition. An attacker can exploit this vulnerability by sending specially crafted requests to the affected system, potentially resulting in the compromise of the system or disruption of services.

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 at the moment. It is highly recommended to apply the official patch or update the linux-libc-dev package to the latest version as soon as possible.

Conclusion

The linux-libc-dev package is vulnerable to a potential Use-After-Free (UAF) vulnerability in the cifs_signal_cifsd_for_reconnect() function. This vulnerability can be exploited to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with kernel privileges. It is crucial to update the linux-libc-dev package to version 6.1.90-1 or later to mitigate this vulnerability. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

The linux-libc-dev package is a development package that provides the necessary header files and libraries for compiling programs that use the Linux kernel interfaces.

A Use-After-Free (UAF) vulnerability is a type of memory corruption issue where a program continues to use a memory region after it has been freed, leading to potential security vulnerabilities.

The potential consequences of this vulnerability include denial-of-service (DoS) conditions and the possibility of arbitrary code execution with kernel privileges.

To update the linux-libc-dev package, you can use the package manager of your Linux distribution. For example, on Debian-based systems, you can use the 'apt-get' command to update the package.

Currently, there is no known workaround for this vulnerability. It is recommended to apply the official patch or update the linux-libc-dev package to the latest version.

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