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-26858net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map

Description

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map Just simply reordering the functions mlx5e_ptp_metadata_map_put and mlx5e_ptpsq_track_metadata in the mlx5e_txwqe_complete context is not good enough since both the compiler and CPU are free to reorder these two functions. If reordering does occur, the issue that was supposedly fixed by 7e3f3ba97e6c ("net/mlx5e: Track xmit submission to PTP WQ after populating metadata map") will be seen. This will lead to NULL pointer dereferences in mlx5e_ptpsq_mark_ts_cqes_undelivered in the NAPI polling context due to the tracking list being populated before the metadata map.

Timeline

  1. ID reserved

    By Linux

  2. · 58 days later

    Published

  3. · 2 years 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-26858, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.23% · top 86% of all CVEs (17 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 4d510506b46504664eacf8a44a9e8f3e54c137b8 – < d1f71615dbb305f14f3b756cce015d70d8667549
    • affected 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167 – < 936ef086161ab89a7f38f7a0761d6a3063c3277e
    • affected 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167 – < b7cf07586c40f926063d4d09f7de28ff82f62b2a
    • affected a9d6c0c5a6bd9ca88e964f8843ea41bc085de866
    • affected 6.6.3 – < 6.6.22
    • affected 6.5.13 – < 6.6
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • unaffected 6.6.22 – ≤ 6.6.*
    • unaffected 6.7.10 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .