CVE-2025-40062: crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 1750f1ec143ebabdbdfa013668665c9d5042c430, 6.1.156, 6.10.
Low priority for now. Upgrade to Linux Linux 1750f1ec143ebabdbdfa013668665c9d5042c430, 6.1.156, 6.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 28, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e0a2d2df9ba7bd6bd7e0a9b6a5e3894f7e8445b3, 6.10affected
- eda60520cfe3aba9f088c68ebd5bcbca9fc6ac3c and later · before a7836260d5121949ba734e840d42a86ab4a32fccaffected · git
- 7fc8d9a525b5c3f8dfa5ed50901e764d8ede7e1e and later · before 1750f1ec143ebabdbdfa013668665c9d5042c430affected · git
- 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and later · before a87a21a56244b8f4eb357f6bad879247005bbe38affected · git
- 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and later · before 7226a0650ad5705bd8d39a11be270fa21ed1e6a5affected · git
- 8be0913389718e8d27c4f1d4537b5e1b99ed7739 and later · before f0cafb02de883b3b413d34eb079c9680782a9cc1affected · git
- 6.1.98 and later · before 6.1.156affected · semver
- 6.6.39 and later · before 6.6.112affected · semver
- 6.9.9 and later · before 6.10affected · semver
- before 6.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40060Oct 28, 2025 · coresight: trbe: Return NULL pointer for allocation failures0Monitor
- ← EarlierCVE-2025-40061Oct 28, 2025 · RDMA/rxe: Fix race in do_task() when draining31Monitor
- Later →CVE-2025-40063Oct 28, 2025 · crypto: comp - Use same definition of context alloc and free ops28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1750f1ec143ebabdbdfa013668665c9d5042c430 | Vendor (CNA) |
| Linux Linux | 6.1.156 | Vendor (CNA) |
| Linux Linux | 6.10 | Vendor (CNA) |
| Linux Linux | 6.6.112 | Vendor (CNA) |
| Linux Linux | 7226a0650ad5705bd8d39a11be270fa21ed1e6a5 | Vendor (CNA) |
| Linux Linux | a7836260d5121949ba734e840d42a86ab4a32fcc | Vendor (CNA) |
| Linux Linux | a87a21a56244b8f4eb357f6bad879247005bbe38 | Vendor (CNA) |
| Linux Linux | f0cafb02de883b3b413d34eb079c9680782a9cc1 | Vendor (CNA) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.