net/mlx5: E-switch, Create ingress ACL when needed
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3e3551f8702978cd2221d2614ca6d6727e785324, Kernel 83bc1a129f7fd0d7d05036ceb7ee69102624e320, Kernel b20c2fb45470d0c7a603613c9cfa5d45720e17f2 and 1 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.18, >=1749c4c51c16e3e078faae0a876d01bafb187a74 <3e3551f8702978cd2221d2614ca6d6727e785324, >=1749c4c51c16e3e078faae0a876d01bafb187a74 <83bc1a129f7fd0d7d05036ceb7ee69102624e320, >=1749c4c51c16e3e078faae0a876d01bafb187a74 <b20c2fb45470d0c7a603613c9cfa5d45720e17f2, >=1749c4c51c16e3e078faae0a876d01bafb187a74 <bc3ff8d3c05044de57865ebbb78cca8f7da3e595 | 3e3551f8702978cd2221d2614ca6d6727e785324, 83bc1a129f7fd0d7d05036ceb7ee69102624e320, b20c2fb45470d0c7a603613c9cfa5d45720e17f2, bc3ff8d3c05044de57865ebbb78cca8f7da3e595 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket