Use After Free Vulnerability in ethernet:enic Package

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1000449: ethernet:enic: Fix a use after free bug in enic_hard_start_xmit. Affects Kernel versions >= fb7516d42478ebc8e2f00efb76ef96f7b68fd8d3, < 25a87b1f566b5eb2af2857a928f0e2310d900976. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ethernet:enic package is a component of the Linux Kernel, which is responsible for managing Ethernet network interfaces. It provides the necessary functionality for transmitting and receiving network packets. The enic_hard_start_xmit function in this package is used to initiate the transmission of Ethernet packets. However, a use after free vulnerability has been discovered in this function.

Vulnerability Detail

The use after free vulnerability in enic_hard_start_xmit arises from improper memory management. When a network packet is being transmitted, the function does not correctly handle the deallocation of memory, leading to a situation where the memory is accessed after it has been freed. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial of service by manipulating the freed memory. The vulnerability was introduced in version v4.16 of the Linux Kernel and has been fixed in version v4.19.191.

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 essential to apply the patch provided in the updated version of the Linux Kernel to mitigate the risk.

Conclusion

The use after free vulnerability in the ethernet:enic package of the Linux Kernel can potentially allow an attacker to execute arbitrary code or cause a denial of service. It is crucial to update the Linux Kernel to version v4.19.191 or later to fix this vulnerability. No known workaround exists, and it is recommended to apply the provided patch to ensure proper memory management during packet transmission. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use after free vulnerability in ethernet:enic can potentially allow an attacker to execute arbitrary code or cause a denial of service by manipulating freed memory.

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, and Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the patch to prevent any potential exploitation.

No, there is no known workaround for this vulnerability. It is necessary to update the Linux Kernel to the fixed version to mitigate the risk.

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