CVE-2024-26858

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

MEDIUM
5.5
CVSS Score
Published: April 17, 2024 at 10:17 AM UTC
Updated: June 17, 2026 at 07:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.5.136.5.13 ≤ v < 6.66.6.3 ≤ v < 6.6.226.7 ≤ v < 6.7.106.7 ≤ v < 6.84d510506b46504664eacf8a44a9e8f3e54c137b86.5.136.6.36.8 rc16.8 rc26.8 rc36.8 rc46.8 rc56.8 rc66.8 rc77e3f3ba97e6cc6fce5bf62df2ca06c8e59040167a9d6c0c5a6bd9ca88e964f8843ea41bc085de866
Vendor states this is fixed in 936ef086161ab89a7f38f7a0761d6a3063c3277e (fixed)
Vendor states this is fixed in b7cf07586c40f926063d4d09f7de28ff82f62b2a (fixed)
Vendor states this is fixed in d1f71615dbb305f14f3b756cce015d70d8667549 (fixed)
Affected range stops below 6.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.22 (unaffected)
Vendor states this is fixed in 6.7 (unaffected)
Vendor states this is fixed in 6.7.10 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (3)

Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card