Skip to main content
No exploitation reportedFix available

CVE-2024-35960

No exploitation reported by the sources we read.

  • Published2024-05-20
  • Fixed inde0139719cdd · adf67a03af39 · 7aaee12b804c · 7c6782ad4911 · 6.8.7 · 6.6.28
  • WeaknessCWE-476

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-05-2010:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-35960?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-35960?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

CISA-ADP · NVD
Linux linux kernel
BranchAffectedFixed in
74491+≥ 74491de93712, < de0139719cddde0139719cdd
74491+≥ 74491de93712, < adf67a03af39adf67a03af39
7.x≥ 74491de93712, < 7aaee12b804c7aaee12b804c
7.x≥ 74491de93712, < 7c6782ad49117c6782ad4911
6.x≥ 6.7, < 6.8.76.8.7
6.x≥ 6.2, < 6.6.286.6.28
6.1≥ 5.16, < 6.1.876.1.87
5.x≥ 5.11, < 5.15.1565.15.156
5.x≥ 5.5, < 5.10.2165.10.216
5.4≥ 4.20, < 5.4.2755.4.275
5.x≥ 74491de93712, < 5cf5337ef7015cf5337ef701
4.x≥ 4.10, < 4.19.3134.19.313
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bpftoolAlmaLinux:9all versions · fixed in 7.3.0-427.24.1.el9_4
  • kernelAlmaLinux:9all versions · fixed in 5.14.0-427.24.1.el9_4and 60 other packages
  • kernelAlmaLinux:8all versions · fixed in 4.18.0-553.8.1.el8_10and 24 other packages
  • kernel-rtAlmaLinux:8all versions · fixed in 4.18.0-553.8.1.rt7.349.el8_10and 11 other packages

Full record on NVD

Fix

  1. Update Linux linux kernel to de0139719cdd · adf67a03af39 · 7aaee12b804c · 7c6782ad4911 · 6.8.7 · 6.6.28 · 6.1.87 · 5.15.156

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Published
2024-05-20
Last Modified
2026-10-15
NVD status
Modified

Frequently asked questions

What is CVE-2024-35960?

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.

Is CVE-2024-35960 actively exploited?

Active exploitation of CVE-2024-35960 has not been confirmed. Its EPSS score was 1.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-35960?

CVE-2024-35960 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database