Vulnerability in Kernel: Incomplete Closure of File Descriptor

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001678: binder: make sure fd closes complete. Affects Kernel versions >= 80cd795630d6526ba729a089a435bf74a57af927, < d5b0473707fa53b03a5db0256ce62b2874bddbc7. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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 handles device drivers. The vulnerability identified in the Kernel pertains to the incomplete closure of a file descriptor, which can lead to potential security risks.

Vulnerability Detail

The vulnerability arises from a flaw in the binder subsystem of the Kernel. When closing a file descriptor (fd), the process does not ensure complete closure, potentially leaving the file descriptor open for unauthorized access. This vulnerability can be exploited by malicious actors to gain unauthorized access to sensitive information or execute arbitrary code within the affected system. It is important to note that the impact and plausibility of an attack have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

To address this vulnerability, it is recommended to update the Linux Kernel to version v5.10.70 or later. The fix for this issue was implemented in commit d5b0473707fa53b03a5db0256ce62b2874bddbc7. Updating the Kernel to the latest version ensures that the flaw is patched and the system is protected against potential exploitation.

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

Workaround

As a workaround, users can manually close the file descriptor after use to ensure complete closure. Here is an example of how to close a file descriptor in C programming language:

#include <unistd.h>

int main() {
    int fd = open("file.txt", O_RDONLY);
    // Perform operations with the file descriptor
    close(fd); // Close the file descriptor
    return 0;
}

Conclusion

The vulnerability in the Kernel, related to the incomplete closure of file descriptors, poses potential security risks. To address this issue, it is crucial to update the Linux Kernel to version v5.10.70 or later. Additionally, manually closing file descriptors after use can serve as a temporary workaround. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow unauthorized access to sensitive information or enable the execution of arbitrary code within the affected system.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

There is no evidence of this vulnerability being exploited in the wild at the time of discovery. However, it is crucial to apply the recommended fix to mitigate any potential risks.

The vulnerability was introduced in version v5.0 of the Linux Kernel by commit 80cd795630d6526ba729a089a435bf74a57af927. It is fixed in version v5.10.70 and later by commit d5b0473707fa53b03a5db0256ce62b2874bddbc7. Therefore, versions between v5.0 and v5.10.70 are affected.

As a temporary workaround, manually closing the file descriptor after use can help mitigate the vulnerability. However, it is strongly recommended to update the Kernel to the latest version to ensure comprehensive protection.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To address this vulnerability, it is recommended to update the Linux Kernel to version v5.10.70 or later. The fix for this issue was implemented in commit d5b0473707fa53b03a5db0256ce62b2874bddbc7. Updating the Kernel to the latest version ensures that the flaw is patched and the system is protected against potential exploitation.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.