Menu

Star on GitHub · 3.2k

CVE-2025-68172

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 devre…

Published Dec 16, 2025EPSS 0.20%

Overview

CVE-2025-68172 is a known-severity vulnerability. It was published on December 16, 2025.

Technical description

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().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68172?

CVE-2025-68172 is a known-severity vulnerability. It was published on December 16, 2025.

How severe is CVE-2025-68172?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68172?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68172?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68172 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.