Use-after-free vulnerability in aio package

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1002462: aio: fix use-after-free due to missing POLLFREE handling. Affects Kernel versions >= 2c14fa838cbefc23cf1c73ca167ed85b274b2913, < 4105e6a128e8a98455dfc9e6dbb2ab0c33c4497f. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The aio package is a component of the Linux Kernel, which provides support for asynchronous I/O operations. It allows applications to perform I/O operations without blocking the execution of other tasks. The package is an integral part of the Linux Kernel and is widely used in various Linux distributions.

Vulnerability Detail

The identified vulnerability in the aio package is a use-after-free issue caused by missing POLLFREE handling. This vulnerability can be exploited by an attacker to manipulate memory after it has been freed, potentially leading to arbitrary code execution or a system crash. The vulnerability was introduced in version v4.18 of the Linux Kernel and was fixed in version v5.4.165 by commit 4105e6a128e8a98455dfc9e6dbb2ab0c33c4497f.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.165 or later. This can be done by applying the relevant patches or upgrading the Linux Kernel package on the affected system. It is important to ensure that the updated version is compatible with the system and any associated software.

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

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

The use-after-free vulnerability in the aio package of the Linux Kernel can pose a significant security risk. It is crucial to update the Linux Kernel to the fixed version to mitigate the vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in the aio package can potentially allow an attacker to execute arbitrary code or crash the system.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will analyze and alert you if the vulnerability is present.

At the time of this report, there are no known public exploits for this vulnerability. However, it is important to apply the necessary updates to mitigate the risk.

Yes, this vulnerability can be exploited remotely if the affected system is exposed to the internet and the necessary conditions for exploitation are met.

For more details about this vulnerability, you can refer to the source link provided in the vulnerability details section.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.165 or later. This can be done by applying the relevant patches or upgrading the Linux Kernel package on the affected system. It is important to ensure that the updated version is compatible with the system and any associated software.

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.