CVE-2024-26858 json
net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map
published 2024-04-17 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-24120
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.6, 6.6.22, 6.7.10, 6.8
- linux Debian 14, Debian 13 6.7.12-1
debian advisories DEBIAN-CVE-2024-26858
- linux-raspi-realtime Ubuntu Pro Realtime 24.04 LTS 6.8.0-2002.2
ubuntu advisories UBUNTU-CVE-2024-26858
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-427.26.1.el9_4
- rv RHEL 9 5.14.0-427.26.1.el9_4
- perf RHEL 9 5.14.0-427.26.1.el9_4
- rtla RHEL 9 5.14.0-427.26.1.el9_4
- bpftool RHEL 9 7.3.0-427.26.1.el9_4
- libperf RHEL 9 5.14.0-427.26.1.el9_4
- kernel-rt RHEL 9 5.14.0-427.26.1.el9_4
- kernel-64k RHEL 9 5.14.0-427.26.1.el9_4
red hat advisories RHSA-2024:4583
- kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-25.1
- kernel-livepatch-MICRO-6-0-RT_Update_5 Linux Micro 6.1, Linux Micro 6.0 1-1.1
- kernel-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source-rt Linux Micro 6.0 6.4.0-9.1
- kernel-source Linux Micro 6.0 6.4.0-18.1
- kernel-default Linux Micro 6.0 6.4.0-18.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
suse advisories SUSE-SU-2025:20166-1SUSE-SU-2025:20249-1SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2203-1
- kernel AlmaLinux 9 5.14.0-427.26.1.el9_4
- rv AlmaLinux 9 5.14.0-427.26.1.el9_4
- perf AlmaLinux 9 5.14.0-427.26.1.el9_4
- rtla AlmaLinux 9 5.14.0-427.26.1.el9_4
- bpftool AlmaLinux 9 7.3.0-427.26.1.el9_4
- libperf AlmaLinux 9 5.14.0-427.26.1.el9_4
- kernel-rt AlmaLinux 9 5.14.0-427.26.1.el9_4
- kernel-64k AlmaLinux 9 5.14.0-427.26.1.el9_4
almalinux advisories ALSA-2024:4583
- kernel Rocky Linux 9 5.14.0-427.26.1.el9_4
rocky linux advisories RLSA-2024:4583
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-26858 updated cvss 4.1
kernel: net/mlx5e: Use a memory barrier to enforce PTP WQ xmit submission tracking occurs after populating the metadata_map
-
Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-427.26.1.el9_4, perf 5.14.0-427.26.1.el9_4, rtla 5.14.0-427.26.1.el9_4, kernel-devel-matched 5.14.0-427.26.1.el9_4, kernel-64k-devel-matched 5.14.0-427.26.1.el9_4, kernel-debug-devel-matched 5.14.0-427.26.1.el9_4, +6 more Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.3.0-427.26.1.el9_4, kernel 5.14.0-427.26.1.el9_4, kernel-64k 5.14.0-427.26.1.el9_4, kernel-core 5.14.0-427.26.1.el9_4, kernel-tools 5.14.0-427.26.1.el9_4, python3-perf 5.14.0-427.26.1.el9_4, +28 more Red Hat Enterprise Linux CRB (v. 9) libperf 5.14.0-427.26.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.26.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.26.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.26.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.26.1.el9_4 Red Hat Enterprise Linux NFV (v. 9) kernel-rt 5.14.0-427.26.1.el9_4, kernel-rt-kvm 5.14.0-427.26.1.el9_4, kernel-rt-core 5.14.0-427.26.1.el9_4, kernel-rt-modules 5.14.0-427.26.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.26.1.el9_4, kernel-rt-debug-core 5.14.0-427.26.1.el9_4, +6 more Red Hat Enterprise Linux RT (v. 9) kernel-rt 5.14.0-427.26.1.el9_4, kernel-rt-core 5.14.0-427.26.1.el9_4, kernel-rt-modules 5.14.0-427.26.1.el9_4, kernel-rt-debug-core 5.14.0-427.26.1.el9_4, kernel-rt-modules-core 5.14.0-427.26.1.el9_4, kernel-rt-debug-modules 5.14.0-427.26.1.el9_4, +4 morefixed: vendor fix RHSA-2024:4583
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
-
git.kernel.org
/stable/c/d1f71615dbb305f14f3b756cce015d70d8667549
mailing-list, patch
-
git.kernel.org
/stable/c/936ef086161ab89a7f38f7a0761d6a3063c3277e
mailing-list, patch
-
git.kernel.org
/stable/c/b7cf07586c40f926063d4d09f7de28ff82f62b2a
mailing-list, patch
Sources
- CVE List CVE-2024-26858
- NVD CVE-2024-26858
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.