Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-42142, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1749c4c51c16e3e078faae0a876d01bafb187a74 – < bc3ff8d3c05044de57865ebbb78cca8f7da3e595
    • affected 1749c4c51c16e3e078faae0a876d01bafb187a74 – < 3e3551f8702978cd2221d2614ca6d6727e785324
    • affected 1749c4c51c16e3e078faae0a876d01bafb187a74 – < 83bc1a129f7fd0d7d05036ceb7ee69102624e320
    • affected 1749c4c51c16e3e078faae0a876d01bafb187a74 – < b20c2fb45470d0c7a603613c9cfa5d45720e17f2
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.98 – ≤ 6.1.*
    • unaffected 6.6.39 – ≤ 6.6.*
    • unaffected 6.9.9 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-42142 badge
[![CVE-2024-42142](https://cveledger.app/badge/CVE-2024-42142.svg)](https://cveledger.app/cve/CVE-2024-42142)

Record last updated .