Vulnerability in Kernel: Incomplete File Descriptor Closure

Kernel Updated 02 Oct 2025

Summary

19/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001617: binder: make sure fd closes complete. Affects Kernel versions >= 80cd795630d6526ba729a089a435bf74a57af927, < aa2c274c279ff365a06a4cba263f04965895166e. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between processes, and ensures security and stability. This vulnerability affects the Kernel and specifically impacts the binder functionality.

Binder is a mechanism in the Kernel that allows inter-process communication (IPC) between different components of the system. It enables processes to share data and invoke methods across different contexts.

The vulnerability arises from a flaw in the binder code that results in incomplete closure of file descriptors (fd). File descriptors are used to access files, sockets, and other I/O resources in Linux. If a file descriptor is not properly closed, it can lead to resource leaks, potential memory corruption, and other security issues.

Vulnerability Detail

The vulnerability in the Kernel's binder functionality allows file descriptors to remain open, leading to resource leaks and potential security risks. When a file descriptor is not correctly closed, it can result in the consumption of system resources, such as memory or file handles, which may eventually lead to system instability or denial of service.

An attacker could potentially exploit this vulnerability by repeatedly opening file descriptors and not closing them, causing resource exhaustion and impacting the overall system performance. Additionally, if the leaked file descriptors are associated with sensitive resources, an attacker may gain unauthorized access or manipulate those resources.

The vulnerability was introduced in version v5.0 of the Linux Kernel and has been fixed in version v5.4.150.

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

As a temporary workaround, it is possible to mitigate the impact of this vulnerability by implementing a custom solution to ensure proper closure of file descriptors in the binder code. The following code snippet demonstrates a possible workaround:

// Custom workaround to ensure complete closure of file descriptors
void closeFileDescriptor(int fd) {
  // Perform necessary operations to close the file descriptor
}

// Usage example
int main() {
  int fd = open("file.txt", O_RDONLY);
  // Use the file descriptor
  closeFileDescriptor(fd);
  return 0;
}

Conclusion

In conclusion, the vulnerability in the Kernel's binder functionality allows file descriptors to remain open, leading to resource leaks and potential security risks. It is crucial to update the Linux Kernel to version v5.4.150 or later to fix this vulnerability. Alternatively, a temporary workaround can be implemented to ensure proper closure of file descriptors. If you require further support or assistance in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can lead to resource leaks, potential memory corruption, and other security issues. It may result in system instability, denial of service, or unauthorized access to sensitive resources.

An attacker can exploit this vulnerability by repeatedly opening file descriptors and not closing them, causing resource exhaustion and impacting system performance. If the leaked file descriptors are associated with sensitive resources, an attacker may gain unauthorized access or manipulate those resources.

The vulnerability was introduced in version v5.0 of the Linux Kernel. All versions between v5.0 and v5.4.149 (inclusive) are affected. It has been fixed in version v5.4.150.

You can use vulnerability monitoring tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software. You can also use the Vulert playground (https://vulert.com/scanner) without signing up to check if your application is affected.

Yes, a temporary workaround is available. By implementing a custom solution to ensure proper closure of file descriptors in the binder code, you can mitigate the impact of this vulnerability. Refer to the 'workaround' section for more details.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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