CVE-2025-40062

UnknownEPSS 0.18%

Last modified

CVE-2025-40062 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.18%

8.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= eda60520cfe3aba9f088c68ebd5bcbca9fc6ac3c, < a7836260d5121949ba734e840d42a86ab4a32fcc; >= 7fc8d9a525b5c3f8dfa5ed50901e764d8ede7e1e, < 1750f1ec143ebabdbdfa013668665c9d5042c430; >= 8be0913389718e8d27c4f1d4537b5e1b99ed7739, < a87a21a56244b8f4eb357f6bad879247005bbe38; >= 8be0913389718e8d27c4f1d4537b5e1b99ed7739, < 7226a0650ad5705bd8d39a11be270fa21ed1e6a5; >= 8be0913389718e8d27c4f1d4537b5e1b99ed7739, < f0cafb02de883b3b413d34eb079c9680782a9cc1; e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3; >= 6.1.98, < 6.1.156; >= 6.6.39, < 6.6.112; >= 6.9.9, < 6.10
LinuxLinux6.10

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40062?
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.
How severe is CVE-2025-40062?
Severity scoring for CVE-2025-40062 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40062?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-40062?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST