LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46717: net/mlx5e: SHAMPO, Fix incorrect page release

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: SHAMPO, Fix incorrect page release Under the following conditions: 1) No skb created yet 2) header_size == 0 (no SHAMPO header) 3) header_index + 1 % MLX5E_SHAMPO_WQ_HEADER_PER_PAGE == 0 (this is the last page fragment of a SHAMPO header page) a new skb is formed with a page that is NOT a SHAMPO header page (it is a regular data page). Further down in the same function (mlx5e_handle_rx_cqe_mpwrq_shampo()), a SHAMPO header page from header_index is released. This is wrong and it leads to SHAMPO header pages being released more than once.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel networking bug in the mlx5e receive path. Under specific packet-handling conditions, the kernel can release a SHAMPO header page more than once. The public sources do not provide CVSS, impact details, or evidence of exploitation, so urgency should be based on exposure to affected kernels and mlx5e use.

Executive priority

Handle through normal kernel patch governance unless exposed systems are internet-facing, high-throughput, or operationally critical. The lack of severity scoring and exploitation evidence lowers confidence, but kernel memory bugs can carry outsized reliability risk.

Technical view

CVE-2024-46717 is a resolved Linux kernel flaw in mlx5e_handle_rx_cqe_mpwrq_shampo(). When no skb exists, header_size is zero, and the header index reaches the last fragment of a SHAMPO header page, the code can form an skb from a regular data page and incorrectly release a SHAMPO header page, causing double release.

Likely exposure

Most relevant exposure is Linux systems running affected kernel versions with the mlx5e driver and SHAMPO receive handling. Systems without that driver path are less likely to be exposed. The source bundle lists Linux 5.17 through fixed stable releases, but exact exposure should be confirmed through vendor kernel advisories.

Exploitation context

The sources do not claim active exploitation, and the CVE is not marked KEV. The public record describes a kernel memory-management correctness issue, not a remote exploitation method. Treat exploitability as unconfirmed unless vendor or threat-intelligence sources later add evidence.

Researcher notes

The issue is constrained to a specific mlx5e SHAMPO receive path state combination. Sources show multiple stable kernel commits and a Debian LTS reference, but provide no CWE, CVSS, exploitability analysis, or named workaround. Validate exposure through kernel version, driver use, and downstream patch status.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems using mlx5e networking on affected Linux kernel lines.
  • Check Linux distribution advisories for backported fixes and package names.
  • Avoid direct wrangler-style assumptions; use vendor kernel guidance for production remediation.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Identify systems loading or depending on the mlx5e driver.
  • Compare installed kernels against vendor advisories for CVE-2024-46717.
  • Confirm fixed stable commits are present in deployed kernel source or changelog.
  • Review kernel logs for memory warnings, without treating absence as proof.
Prepared
Confidence
medium
Sources
7

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-46717 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
6Source 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
LinuxLinux7957837b816f11eecb9146235bb0715478f4c81f, 7957837b816f11eecb9146235bb0715478f4c81f, 7957837b816f11eecb9146235bb0715478f4c81f, 7957837b816f11eecb9146235bb0715478f4c81f, a4161e4861132d5b324746a260283e87f2d65daf, 5.16.6unaffected
LinuxLinux5.17, 0, 6.1.109, 6.6.50, 6.10.9, 6.11affected
Weakness

CWE details

No CWE listed

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