LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38645: net/mlx5: Check device memory pointer before usage

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Check device memory pointer before usage Add a NULL check before accessing device memory to prevent a crash if dev->dm allocation in mlx5_init_once() fails.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems when the mlx5 networking driver uses device memory after an allocation failure. The public sources describe a missing NULL check, not data theft or privilege escalation. Business impact is most likely availability risk on systems that depend on affected Linux kernels and mlx5 hardware support.

Executive priority

Handle as a kernel availability-risk update, not an emergency based on current evidence. Prioritize patching for infrastructure where a kernel crash would disrupt critical services or clustered capacity.

Technical view

The fix adds a NULL check before accessing dev->dm in net/mlx5 after mlx5_init_once() allocation can fail. Without the check, the kernel may dereference a NULL device-memory pointer and crash. The CVE record lists affected Linux kernel versions but provides no CVSS score or CWE.

Likely exposure

Exposure appears most relevant to Linux systems running affected kernel builds with the mlx5 driver in use. The source bundle lists Linux kernel version entries including 5.4, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, and 6.17.

Exploitation context

No source in the bundle reports active exploitation, and KEV is false. The described condition is a crash triggered by failed device-memory allocation followed by unsafe pointer use. Practical exploitability is not established by the provided evidence.

Researcher notes

The public record is sparse: no CVSS, no CWE, and no exploit details. Analysis should focus on confirming affected kernel lineage, whether mlx5 code is reachable on target systems, and whether downstream vendor packages include one of the stable commits.

Mitigation direction

  • Track vendor kernel advisories for CVE-2025-38645 and apply the fixed kernel updates.
  • Prioritize systems where the mlx5 driver supports production networking workloads.
  • Use distribution-provided kernel packages rather than hand-porting the patch when possible.
  • If patching is delayed, assess operational dependency on affected mlx5-enabled hosts.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify hosts loading or depending on the mlx5 driver.
  • Check whether installed kernels include the referenced stable fixes.
  • Review distribution advisories, including Debian LTS, for package-specific status.
Prepared
Confidence
medium
Sources
10

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-2025-38645 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
1ADP providers
9Source links

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

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481, c9b9dcb430b3cd0ad2b04c360c4e528d73430481unaffected
LinuxLinux5.4, 0, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

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