LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26858: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-26858 is a Linux kernel bug in mlx5e PTP transmit tracking. A memory-ordering issue can let tracking data appear before its metadata is ready, leading to a kernel NULL pointer dereference and likely service disruption on affected systems.

Executive priority

Treat as a targeted kernel stability risk. Prioritize patch validation for network-heavy Linux systems using mlx5e/PTP, but do not escalate as actively exploited based on the provided evidence.

Technical view

The flaw is in net/mlx5e PTP work queue transmit completion handling. Without a required memory barrier, mlx5e_ptpsq_track_metadata can be observed before mlx5e_ptp_metadata_map_put populates metadata_map, causing mlx5e_ptpsq_mark_ts_cqes_undelivered to dereference NULL during NAPI polling.

Likely exposure

Exposure appears limited to Linux kernels in the affected ranges and configurations exercising the mlx5e PTP transmit timestamping path. The source bundle lists Linux as affected, including 6.7, 6.6.22, 6.7.10, and 6.8 entries, but does not provide CPEs.

Exploitation context

No CISA KEV listing is provided, and the cited sources do not state active exploitation. The public description frames this as a resolved kernel correctness issue causing NULL pointer dereferences, not as a proven remote exploit path.

Researcher notes

The key issue is ordering, not just function sequence. The fix enforces that metadata_map population is visible before transmit submission tracking. Impact and triggerability depend on affected kernel version, mlx5e path usage, and runtime timing.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Check distribution kernel advisories for backported CVE-2024-26858 fixes.
  • Prioritize hosts using the kernel mlx5e driver and PTP functionality.
  • If patch timing is uncertain, consult vendor guidance for supported operational mitigations.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems loading or relying on the mlx5e driver.
  • Check whether PTP timestamping features are enabled or required.
  • Confirm installed kernel packages include the referenced stable fix commits.
  • Monitor kernel logs for mlx5e, PTP, NAPI, or NULL dereference crashes.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26858 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4d510506b46504664eacf8a44a9e8f3e54c137b8, 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167, 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167, a9d6c0c5a6bd9ca88e964f8843ea41bc085de866, 6.6.3, 6.5.13unaffected
LinuxLinux6.7, 0, 6.6.22, 6.7.10, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.