CVE-2024-42142

net/mlx5: E-switch, Create ingress ACL when needed

MEDIUM
5.5
CVSS Score
Published: July 30, 2024 at 07:46 AM UTC
Updated: June 17, 2026 at 07:48 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-switch, Create ingress ACL when needed Currently, ingress acl is used for three features. It is created only when vport metadata match and prio tag are enabled. But active-backup lag mode also uses it. It is independent of vport metadata match and prio tag. And vport metadata match can be disabled using the following devlink command: # devlink dev param set pci/0000:08:00.0 name esw_port_metadata \ value false cmode runtime If ingress acl is not created, will hit panic when creating drop rule for active-backup lag mode. If always create it, there will be about 5% performance degradation. Fix it by creating ingress acl when needed. If esw_port_metadata is true, ingress acl exists, then create drop rule using existing ingress acl. If esw_port_metadata is false, create ingress acl and then create drop rule.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.985.18 ≤ v < 6.105.18 ≤ v < 6.6.395.18 ≤ v < 6.9.96.2 ≤ v < 6.6.396.7 ≤ v < 6.9.91749c4c51c16e3e078faae0a876d01bafb187a746.10 rc16.10 rc26.10 rc36.10 rc46.10 rc56.10 rc6
Vendor states this is fixed in 3e3551f8702978cd2221d2614ca6d6727e785324 (fixed)
Vendor states this is fixed in 83bc1a129f7fd0d7d05036ceb7ee69102624e320 (fixed)
Vendor states this is fixed in b20c2fb45470d0c7a603613c9cfa5d45720e17f2 (fixed)
Vendor states this is fixed in bc3ff8d3c05044de57865ebbb78cca8f7da3e595 (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.98 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.6.39 (unaffected)
Vendor states this is fixed in 6.9.9 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/3e3551f8702978cd2221d2614ca6d6727e785324
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/83bc1a129f7fd0d7d05036ceb7ee69102624e320
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b20c2fb45470d0c7a603613c9cfa5d45720e17f2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bc3ff8d3c05044de57865ebbb78cca8f7da3e595
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card