Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35960: net/mlx5: Properly link new fs rules into the tree

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 72.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 1263b0b26077b1183c3c45a0a2479573a351d423, 2e8dc5cffc844dacfa79f056dea88002312f253f, 3d90ca9145f6b97b38d0c2b6b30f6ca6af9c1801.

Low priority for now. Upgrade to Linux Linux 1263b0b26077b1183c3c45a0a2479573a351d423, 2e8dc5cffc844dacfa79f056dea88002312f253f, 3d90ca9145f6b97b38d0c2b6b30f6ca6af9c1801 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
May 20, 2024
Updated
Oct 15, 2026
EPSS
1.4% · 72th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35960

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.275
  • linux linux kernel5.5 and later · before 5.10.216
  • linux linux kernel5.11 and later · before 5.15.156
  • linux linux kernel4.10 and later · before 4.19.313
  • linux linux kernel6.2 and later · before 6.6.28
  • linux linux kernel6.7 and later · before 6.8.7
  • linux linux kernel5.16 and later · before 6.1.87
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.10affected
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before de0139719cdda82806a47580ca0df06fc85e0bd2affected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 1263b0b26077b1183c3c45a0a2479573a351d423affected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 3d90ca9145f6b97b38d0c2b6b30f6ca6af9c1801affected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 7aaee12b804c5e0374e7b132b6ec2158ff33dd64affected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 2e8dc5cffc844dacfa79f056dea88002312f253faffected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 5cf5337ef701830f173b4eec00a4f984adeb57a0affected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before adf67a03af39095f05d82050f15813d6f700159daffected · git
    • 74491de937125d0c98c9b9c9208b4105717a3caa and later · before 7c6782ad4911cbee874e85630226ed389ff2e453affected · git
    • before 4.10not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.24.1.el9_47.3.0-427.24.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.24.1.el9_45.14.0-427.24.1.el9_4

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35955May 20, 2024 · kprobes: Fix possible use-after-free issue on kprobe registration
    35Monitor
  • ← EarlierCVE-2024-35958May 20, 2024 · net: ena: Fix incorrect descriptor free behavior
    22Monitor
  • Later →CVE-2024-35962May 20, 2024 · netfilter: complete validation of user input
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1263b0b26077b1183c3c45a0a2479573a351d423Vendor (CNA)
Linux Linux2e8dc5cffc844dacfa79f056dea88002312f253fVendor (CNA)
Linux Linux3d90ca9145f6b97b38d0c2b6b30f6ca6af9c1801Vendor (CNA)
Linux Linux5cf5337ef701830f173b4eec00a4f984adeb57a0Vendor (CNA)
Linux Linux7aaee12b804c5e0374e7b132b6ec2158ff33dd64Vendor (CNA)
Linux Linux7c6782ad4911cbee874e85630226ed389ff2e453Vendor (CNA)
Linux Linuxadf67a03af39095f05d82050f15813d6f700159dVendor (CNA)
Linux Linuxde0139719cdda82806a47580ca0df06fc85e0bd2Vendor (CNA)
almalinux:bpftool7.3.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.24.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.90-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-core0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-core0:5.14.0-284.71.1.rt14.356.el9_2 · Red Hat:rhel_eus:9.2::nfvPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records