cbcvebase.
CVE-2024-35960
published 2024-05-20

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…

PriorityP350critical9.1CVSS 3.1
AVNACLPRNUINSUCNIHAH
ITW
Exploited in the wild
EPSS
1.40%
69.5th percentile
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.

Affected

27 ranges· showing 25
VendorProductVersion rangeFixed in
debiandebian_linux
debianlinux< linux 6.1.90-1 (bookworm)linux 6.1.90-1 (bookworm)
linuxlinux
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < de0139719cdda82806a47580ca0df06fc85e0bd2de0139719cdda82806a47580ca0df06fc85e0bd2
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 1263b0b26077b1183c3c45a0a2479573a351d4231263b0b26077b1183c3c45a0a2479573a351d423
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 3d90ca9145f6b97b38d0c2b6b30f6ca6af9c18013d90ca9145f6b97b38d0c2b6b30f6ca6af9c1801
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 7aaee12b804c5e0374e7b132b6ec2158ff33dd647aaee12b804c5e0374e7b132b6ec2158ff33dd64
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 2e8dc5cffc844dacfa79f056dea88002312f253f2e8dc5cffc844dacfa79f056dea88002312f253f
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 5cf5337ef701830f173b4eec00a4f984adeb57a05cf5337ef701830f173b4eec00a4f984adeb57a0
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < adf67a03af39095f05d82050f15813d6f700159dadf67a03af39095f05d82050f15813d6f700159d
linuxlinux>= 74491de937125d0c98c9b9c9208b4105717a3caa < 7c6782ad4911cbee874e85630226ed389ff2e4537c6782ad4911cbee874e85630226ed389ff2e453
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.216-15.10.216-1
linuxlinux_kernel>= 0 < 6.1.90-16.1.90-1
linuxlinux_kernel>= 0 < 6.8.9-16.8.9-1
linuxlinux_kernel>= 0 < 6.8.9-16.8.9-1
linuxlinux_kernel>= 0 < 5.4.0-189.2095.4.0-189.209
linuxlinux_kernel>= 0 < 5.15.0-116.1265.15.0-116.126
linuxlinux_kernel>= 0 < 6.8.0-38.386.8.0-38.38
linuxlinux_kernel>= 0 < 4.15.0-236.2484.15.0-236.248
linuxlinux_kernel>= 4.10 < 4.19.3134.19.313
linuxlinux_kernel>= 4.20 < 5.4.2755.4.275
linuxlinux_kernel>= 5.11 < 5.15.1565.15.156
linuxlinux_kernel>= 5.16 < 6.1.876.1.87
linuxlinux_kernel>= 5.5 < 5.10.2165.10.216

CVSS provenance

nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
osv9.1CRITICAL
vendor_debian9.1CRITICAL
vendor_redhat9.1CRITICAL
vendor_ubuntu7.1HIGH
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.