LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40062: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs

In the Linux kernel, the following vulnerability has been resolved: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs When the initialization of qm->debug.acc_diff_reg fails, the probe process does not exit. However, after qm->debug.qm_diff_regs is freed, it is not set to NULL. This can lead to a double free when the remove process attempts to free it again. Therefore, qm->debug.qm_diff_regs should be set to NULL after it is freed.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-40062 is a Linux kernel defect in the HiSilicon QM crypto driver. A failed debug initialization can leave a freed pointer uncleared, causing a later cleanup path to free it again. The public data does not provide a CVSS score, confirmed exploit activity, or a complete business-impact statement.

Executive priority

Treat as a targeted kernel maintenance item rather than an emergency based on current evidence. Prioritize affected Linux hosts using the relevant HiSilicon driver, and fold remediation into normal kernel update governance unless vendor guidance raises urgency.

Technical view

In crypto/hisilicon/qm, qm->debug.qm_diff_regs is freed after qm->debug.acc_diff_reg initialization fails, but is not set to NULL. Because probe continues, later remove handling may free qm_diff_regs again. Stable kernel commits set the pointer to NULL after free.

Likely exposure

Most relevant exposure is Linux systems running affected kernel builds where the hisilicon/qm crypto driver is present or loaded. Generic Linux systems without this driver path appear less likely exposed. Distro backport status is not included in the bundle.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit code. It describes a double-free condition, but not prerequisites, attacker control, privilege requirements, or real-world exploitation impact.

Researcher notes

Evidence is limited to the CVE description and stable kernel commit references. The impact is a double free in a driver cleanup path after a specific initialization failure. The bundle does not establish exploitability, local versus remote reachability, or affected distro package ranges.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2025-40062 status.
  • Update to a kernel containing the referenced stable fixes when available.
  • Prioritize systems using HiSilicon QM crypto acceleration or loading hisilicon/qm.
  • If patching is delayed, review vendor guidance for driver-specific workarounds.

Validation and detection

  • Inventory Linux kernel versions and compare against vendor CVE-2025-40062 advisories.
  • Check whether the hisilicon/qm driver is present or loaded on relevant systems.
  • Confirm installed kernel packages include the referenced stable fix commits or vendor backports.
  • Document any unpatched systems and compensating controls for vulnerability management tracking.
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-2025-40062 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
6Source 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
LinuxLinuxeda60520cfe3aba9f088c68ebd5bcbca9fc6ac3c, 7fc8d9a525b5c3f8dfa5ed50901e764d8ede7e1e, 8be0913389718e8d27c4f1d4537b5e1b99ed7739, 8be0913389718e8d27c4f1d4537b5e1b99ed7739, 8be0913389718e8d27c4f1d4537b5e1b99ed7739, e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3, 6.1.98, 6.6.39, 6.9.9unaffected
LinuxLinux6.10, 0, 6.1.156, 6.6.112, 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.