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

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-07-30 · updated 2026-06-17

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 products

Linux kernel: from 5.18 before 6.1.98; from 6.2 before 6.6.39; from 6.7 before 6.9.9; 6.10-rc1, 6.10-rc2, 6.10-rc3, 6.10-rc4, 6.10-rc5, 6.10-rc6 — fixed in 6.1.98, 6.6.39, 6.9.9

How to fix

Upgrade to a fixed version: Linux kernel 6.1.98, 6.6.39, 6.9.9. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-42142 or the next vulnerability affects your stack