All Threat Alerts
criticalCVE Alert
CVE-2024-35960

Critical Vulnerability: CVE-2024-35960 โ€” linux, debian โ€” linux_kernel, debian_linux

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

Thursday, October 15, 2026linuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

CVE-2024-35960 is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: linux_kernel, debian_linux.

Executive Summary

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

Why It Matters

CVE-2024-35960 is rated CRITICAL severity, requiring immediate attention from security teams.

CVSS Base Score: 9.1/10

Affected Technologies

Vendors: linux, debian

Products: linux_kernel, debian_linux

๐Ÿ›ก๏ธWhat Defenders Should Check

  • Check if you are affected โ€” Review your asset inventory for products listed in CVE-2024-35960.
  • Apply available patches โ€” Visit vendor advisories for the latest security updates.
  • Monitor for exploitation โ€” Check your SIEM/IDS logs for related indicators.
  • Use Vulnios to continuously monitor your exposure to CVE-2024-35960 and similar vulnerabilities.

    References & Sources

    How Vulnios Detects This

    Vulnios scans for this vulnerability using Trivy and Grype for CVE matching against your container images and OS package manifests. Run a scan against your environment to see whether you are exposed; findings are linked back to the original CVE record so triage starts with the patch path already known.

    AI Security Advisor

    Powered by Gemini

    Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

    Affected Products

    linux_kerneldebian_linux

    Sources

    Related Threat Alerts

    Frequently Asked Questions

    What is CVE-2024-35960?

    CVE-2024-35960 is a critical-severity vulnerability tracked under the Common Vulnerabilities and Exposures program. 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

    Am I affected?

    Check whether your environment runs linux_kernel, debian_linux. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

    How urgent is the response?

    Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

    How do I remediate?

    Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

    Where can I track exploitation activity?

    Watch CISA's Known Exploited Vulnerabilities catalog for CVE-2024-35960. Cross-reference with public exploit databases and your own SIEM/IDS for indicator-of-compromise patterns. Vulnios tracks KEV status automatically and surfaces it on the asset findings view.

    How does Vulnios help with this?

    Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

    critical

    Protect Your Organization

    Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

    Weekly threat digest

    KEV-listed exploits and vendor advisories, every Monday.

    One email a week. Unsubscribe any time.

    Get instant alerts on Telegram

    Join our public channel for real-time critical CVE alerts.

    Follow @vulnios