CVE-2024-35960 Details
Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Properly link new fs rules into the tree Previously, add_rule_fg would only add newly created rules from the handle into the tree when they had a refcount of 1. On the other hand, create_flow_handle tries hard to find and reference already existing identical rules instead of creating new ones. These two behaviors can result in a situation where create_flow_handle 1) creates a new rule and references it, then 2) in a subsequent step during the same handle creation references it again, resulting in a rule with a refcount of 2 that is not linked into the tree, will have a NULL parent and root and will result in a crash when the flow group is deleted because del_sw_hw_rule, invoked on rule deletion, assumes node->parent is != NULL. This happened in the wild, due to another bug related to incorrect handling of duplicate pkt_reformat ids, which lead to the code in create_flow_handle incorrectly referencing a just-added rule in the same flow handle, resulting in the problem described above. Full details are at [1]. This patch changes add_rule_fg to add new rules without parents into the tree, properly initializing them and avoiding the crash. This makes it more consistent with how rules are added to an FTE in create_flow_handle.
A vulnerability in the Linux kernel's handling of flow rules can lead to a denial-of-service condition. This issue arises in the Mellanox mlx5 networking component, where newly created flow rules may not be properly linked into the management tree. The problem occurs when a flow rule is referenced multiple times during its creation process, resulting in a reference count that indicates the rule is in use, but the rule is not actually linked into the tree structure. Consequently, when the flow group is deleted, the system attempts to remove the rule but encounters a crash because it expects the rule to be properly linked. This vulnerability has been observed in the wild, triggered by a separate bug that caused incorrect handling of duplicate packet reformatting identifiers, leading to the creation of unlinked rules.
Users can update to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 16, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.10, < 4.19.313 >= 4.20, < 5.4.275 >= 5.5, < 5.10.216 >= 5.11, < 5.15.156 >= 5.16, < 6.1.87 >= 6.2, < 6.6.28 >= 6.7, < 6.8.7 6.9 rc1 6.9 rc2 6.9 rc3 |
CPE
Remediation
| |
| debian debian linux | 10.0 |
CPE
Remediation
| |
Change History
15 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Oct 15, 2026 | CVE Modified | CVE |
| Jun 17, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 12, 2026 | CVE Modified | siemens-SADP |
| Apr 4, 2025 | Initial Analysis | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| Nov 5, 2024 | CVE Modified | kernel.org |
| Jul 3, 2024 | CVE Modified | CISA-ADP |
| Jun 27, 2024 | CVE Modified | kernel.org |
| Jun 25, 2024 | CVE Modified | kernel.org |
| May 29, 2024 | CVE Modified | kernel.org |
| May 20, 2024 | New CVE Received | kernel.org |