net/mlx5: Delete FTE when no rules are attached
Summary
GSD-2022-1003604: net/mlx5: fs, delete the FTE when there are no rules attached to it. Affects Kernel versions < 9b42659cb3c44caa605ee1a9f91147d7bff16bf1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The net/mlx5 package is a component of the Linux Kernel that provides support for Mellanox ConnectX network adapters. It includes functionality for managing flow tables and rules for packet processing. The vulnerability in question relates to the failure to delete a Flow Table Entry (FTE) when there are no rules attached to it.
Vulnerability Detail
The vulnerability in net/mlx5 allows for the persistence of FTEs even when there are no associated rules. This can lead to resource wastage and potential performance degradation. An attacker could potentially exploit this vulnerability by creating a large number of FTEs without any rules, causing a denial-of-service condition or consuming excessive system resources.
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 →
Conclusion
The net/mlx5 vulnerability allows for the persistence of unused Flow Table Entries, potentially leading to resource wastage and performance issues. It is crucial to update the Linux Kernel to the recommended version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
net/mlx5 is a component of the Linux Kernel that provides support for Mellanox ConnectX network adapters.
A Flow Table Entry (FTE) is a data structure used in net/mlx5 to represent a rule for packet processing.
The vulnerability can lead to resource wastage and potential performance degradation. It may also be exploited for denial-of-service attacks or excessive resource consumption.
To fix this vulnerability, update the Linux Kernel to version v5.10.121 or later, which includes the necessary fix commit.
No specific workaround has been provided for this vulnerability. Updating the Linux Kernel is the recommended solution.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
