Menu

Star on GitHub · 3.2k

CVE-2025-68732

In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Fix race in syncpt alloc/free Fix race condition between host1x_syncpt_alloc() and host1x_syncpt_put() by using kr…

Published Dec 24, 2025EPSS 0.19%

Overview

CVE-2025-68732 is a known-severity vulnerability. It was published on December 24, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

gpu: host1x: Fix race in syncpt alloc/free

Fix race condition between host1x_syncpt_alloc()

and host1x_syncpt_put() by using kref_put_mutex()

instead of kref_put() + manual mutex locking.

This ensures no thread can acquire the

syncpt_mutex after the refcount drops to zero

but before syncpt_release acquires it.

This prevents races where syncpoints could

be allocated while still being cleaned up

from a previous release.

Remove explicit mutex locking in syncpt_release

as kref_put_mutex() handles this atomically.

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-68732?

CVE-2025-68732 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2025-68732?

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-68732?

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-68732?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68732 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.