CVE-2025-68172: crypto: aspeed - fix double free caused by devm
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 0dd6474ced33489076e6c0f3fe5077bf12e85b28, 29d0504077044a7e1ffbd09a6118018d5954a6e5, 3c9bf72cc1ced1297b235f9422d62b613a3fdae9.
Low priority for now. Upgrade to Linux Linux 0dd6474ced33489076e6c0f3fe5077bf12e85b28, 29d0504077044a7e1ffbd09a6118018d5954a6e5, 3c9bf72cc1ced1297b235f9422d62b613a3fdae9 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: aspeed - fix double free caused by devm The clock obtained via devm_clk_get_enabled() is automatically managed by devres and will be disabled and freed on driver detach. Manually calling clk_disable_unprepare() in error path and remove function causes double free. Remove the manual clock cleanup in both aspeed_acry_probe()'s error path and aspeed_acry_remove().
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.2% · 10th 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.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 6.3affected
- 2f1cf4e50c956f882c9fc209c7cded832b67b8a3 and later · before 0dd6474ced33489076e6c0f3fe5077bf12e85b28affected · git
- 2f1cf4e50c956f882c9fc209c7cded832b67b8a3 and later · before 29d0504077044a7e1ffbd09a6118018d5954a6e5affected · git
- 2f1cf4e50c956f882c9fc209c7cded832b67b8a3 and later · before e8407dfd267018f4647ffb061a9bd4a6d7ebacc6affected · git
- 2f1cf4e50c956f882c9fc209c7cded832b67b8a3 and later · before 3c9bf72cc1ced1297b235f9422d62b613a3fdae9affected · git
- before 6.3not affected · semver
- 6.6.117 and later · up to and including 6.6.*not affected · semver
- 6.12.58 and later · up to and including 6.12.*not affected · semver
- 6.17.8 and later · up to and including 6.17.*not affected · semver
- 6.18 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-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-68170Dec 16, 2025 · drm/radeon: Do not kfree() devres managed rdev31Monitor
- ← EarlierCVE-2025-68171Dec 16, 2025 · x86/fpu: Ensure XFD state on signal delivery31Monitor
- Later →CVE-2025-68173Dec 16, 2025 · ftrace: Fix softlockup in ftrace_module_enable0Monitor
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 | 0dd6474ced33489076e6c0f3fe5077bf12e85b28 | Vendor (CNA) |
| Linux Linux | 29d0504077044a7e1ffbd09a6118018d5954a6e5 | Vendor (CNA) |
| Linux Linux | 3c9bf72cc1ced1297b235f9422d62b613a3fdae9 | Vendor (CNA) |
| Linux Linux | e8407dfd267018f4647ffb061a9bd4a6d7ebacc6 | Vendor (CNA) |
| debian:linux | 6.12.63-1 · Debian:13 | 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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.