LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40059: coresight: Fix incorrect handling for return value of devm_kzalloc

In the Linux kernel, the following vulnerability has been resolved: coresight: Fix incorrect handling for return value of devm_kzalloc The return value of devm_kzalloc could be an null pointer, use "!desc.pdata" to fix incorrect handling return value of devm_kzalloc.

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 bug in CoreSight tracing/debug support. It concerns mishandling a failed memory allocation. The public record does not rate severity or describe real-world attacks. Treat it as a kernel maintenance exposure until distro/vendor advisories clarify impact.

Executive priority

Track through normal kernel patch governance unless CoreSight-enabled ARM or embedded systems are business-critical. Severity is not established, so urgency should come from asset exposure and vendor advisories rather than public exploitation pressure.

Technical view

The bug is in Linux kernel CoreSight code. A devm_kzalloc allocation result was checked incorrectly; allocation can return NULL, and the fix tests !desc.pdata. Sources do not provide CVSS, CWE, crash path, privilege boundary, or proof of exploitability.

Likely exposure

Likely exposure is Linux systems running affected kernels with CoreSight driver code present, especially ARM or embedded environments using CoreSight tracing/debug components. The record does not identify affected distributions, configurations, attack vectors, or whether typical server deployments are reachable.

Exploitation context

No active exploitation is supported by the provided evidence. The KEV flag is false, and the cited references are kernel stable fixes. The source bundle gives no public exploit, attacker prerequisites, or operational impact beyond the null-pointer handling flaw.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability details, or distribution mapping. Analysis should focus on confirming affected kernel branches, locating the exact stable commits in downstream packages, and determining whether local CoreSight code paths are built and reachable.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable CoreSight fixes.
  • Check distribution advisories for backported fixes and supported kernel package names.
  • Prioritize ARM or embedded Linux systems using CoreSight functionality.
  • If no vendor guidance exists, track the cited upstream stable commits.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Check whether CoreSight-related kernel modules or configuration are present.
  • Confirm installed kernel packages include the referenced upstream fixes or distro backports.
  • Record that no KEV-listed exploitation is cited in the provided sources.
Prepared
Confidence
medium
Sources
5

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-40059 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
0ADP providers
4Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4277f035d227e829133df284be7e35b7236a5b0f, 4277f035d227e829133df284be7e35b7236a5b0f, 4277f035d227e829133df284be7e35b7236a5b0funaffected
LinuxLinux6.8, 0, 6.12.53, 6.17.3, 6.18affected
Weakness

CWE details

No CWE listed

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