Use-after-free vulnerability in i40e_client_subtask() in Kernel

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000204: i40e: Fix use-after-free in i40e_client_subtask(). Affects Kernel versions >= 7b0b1a6d0ac983ce1928432285d0222d4fb7c38b, < 1fd5d262e7442192ac7611ff1597a36c5b044323. 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 fundamental component of the Linux operating system that provides core functionalities and acts as an interface between the hardware and software layers. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. The i40e_client_subtask() function is a part of the i40e driver, which is responsible for managing Intel Ethernet Connection X710/XL710 devices. This vulnerability specifically affects the i40e_client_subtask() function in the Kernel.

Vulnerability Detail

The use-after-free vulnerability in i40e_client_subtask() allows an attacker to exploit a freed memory region, leading to potential memory corruption or arbitrary code execution. This vulnerability was introduced in version v4.16 of the Linux Kernel by commit 7b0b1a6d0ac983ce1928432285d0222d4fb7c38b. It was fixed in version v5.12.5 by commit 1fd5d262e7442192ac7611ff1597a36c5b044323. The impact and attack plausibility of this vulnerability have not been proven yet.

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. It is crucial to update to the fixed version of the Linux Kernel to mitigate the risk.

Conclusion

The use-after-free vulnerability in i40e_client_subtask() poses a potential risk of memory corruption or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.12.5 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The i40e_client_subtask() function is a part of the i40e driver in the Linux Kernel. It is responsible for managing Intel Ethernet Connection X710/XL710 devices.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed. This can lead to memory corruption or arbitrary code execution.

The use-after-free vulnerability in i40e_client_subtask() can be exploited by an attacker to manipulate freed memory and potentially execute arbitrary code.

There is no evidence of this vulnerability being exploited in the wild. However, it is important to apply the fix to ensure system security.

No, only versions from v4.16 to v5.12.4 are affected. The vulnerability was fixed in version v5.12.5.

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