Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 6.6, 6.6.22, 936ef086161ab89a7f38f7a0761d6a3063c3277e.

Low priority for now. Upgrade to Linux Linux 6.6, 6.6.22, 936ef086161ab89a7f38f7a0761d6a3063c3277e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26858

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.5.13 and later · before 6.6
  • linux linux kernel6.6.3 and later · before 6.6.22
  • linux linux kernel6.7 and later · before 6.7.10
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • a9d6c0c5a6bd9ca88e964f8843ea41bc085de866, 6.7affected
    • 4d510506b46504664eacf8a44a9e8f3e54c137b8 and later · before d1f71615dbb305f14f3b756cce015d70d8667549affected · git
    • 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167 and later · before 936ef086161ab89a7f38f7a0761d6a3063c3277eaffected · git
    • 7e3f3ba97e6cc6fce5bf62df2ca06c8e59040167 and later · before b7cf07586c40f926063d4d09f7de28ff82f62b2aaffected · git
    • 6.6.3 and later · before 6.6.22affected · semver
    • 6.5.13 and later · before 6.6affected · semver
    • before 6.7not affected · semver
    • 6.6.22 and later · up to and including 6.6.*not affected · semver
    • 6.7.10 and later · up to and including 6.7.*not affected · semver
    • 6.8 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.26.1.el9_47.3.0-427.26.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.26.1.el9_45.14.0-427.26.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26856Apr 17, 2024 · net: sparx5: Fix use after free inside sparx5_del_mact_entry
    31Monitor
  • ← EarlierCVE-2024-26857Apr 17, 2024 · geneve: make sure to pull inner header in geneve_rx()
    29Monitor
  • Later →CVE-2024-26860Apr 17, 2024 · dm-integrity: fix a memory leak when rechecking the data
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux6.6Vendor (CNA)
Linux Linux6.6.22Vendor (CNA)
Linux Linux936ef086161ab89a7f38f7a0761d6a3063c3277eVendor (CNA)
Linux Linuxb7cf07586c40f926063d4d09f7de28ff82f62b2aVendor (CNA)
Linux Linuxd1f71615dbb305f14f3b756cce015d70d8667549Vendor (CNA)
almalinux:bpftool7.3.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.26.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.7.12-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.26.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records