CVE-2025-68732: gpu: host1x: Fix race in syncpt alloc/free
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 4aeaece518fa4436af93d1d8b786200d9656ff4b, 4e6e07ce0197aecfb6c4a62862acc93b3efedeb7, 6245cce711e2cdb2cc75c0bb8632952e36f8c972; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 4aeaece518fa4436af93d1d8b786200d9656ff4b, 4e6e07ce0197aecfb6c4a62862acc93b3efedeb7, 6245cce711e2cdb2cc75c0bb8632952e36f8c972; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 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: 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.
- Published
- Dec 24, 2025
- Updated
- Oct 13, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
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
- 5.13affected
- f5ba33fb9690566c382624637125827b5512e766 and later · before ca9388fba50dac2eb71c13702b7022a801bef90eaffected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before 4aeaece518fa4436af93d1d8b786200d9656ff4baffected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before 6245cce711e2cdb2cc75c0bb8632952e36f8c972affected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before 4e6e07ce0197aecfb6c4a62862acc93b3efedeb7affected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before d138f73ffb0c57ded473c577719e6e551b7b1f27affected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before 79197c6007f2afbfd7bcf5b9b80ccabf8483d774affected · git
- f5ba33fb9690566c382624637125827b5512e766 and later · before c7d393267c497502fa737607f435f05dfe6e3d9baffected · git
- before 5.13not affected · semver
- 5.15.198 and later · up to and including 5.15.*not 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.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-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-68730Dec 24, 2025 · accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context()31Monitor
- ← EarlierCVE-2025-68731Dec 24, 2025 · accel/amdxdna: Fix an integer overflow in aie2_query_ctx_status_array()0Monitor
- Later →CVE-2025-68733Dec 24, 2025 · smack: fix bug: unprivileged task can create labels0Monitor
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 | 4aeaece518fa4436af93d1d8b786200d9656ff4b | Vendor (CNA) |
| Linux Linux | 4e6e07ce0197aecfb6c4a62862acc93b3efedeb7 | Vendor (CNA) |
| Linux Linux | 6245cce711e2cdb2cc75c0bb8632952e36f8c972 | Vendor (CNA) |
| Linux Linux | 79197c6007f2afbfd7bcf5b9b80ccabf8483d774 | Vendor (CNA) |
| Linux Linux | c7d393267c497502fa737607f435f05dfe6e3d9b | Vendor (CNA) |
| Linux Linux | ca9388fba50dac2eb71c13702b7022a801bef90e | Vendor (CNA) |
| Linux Linux | d138f73ffb0c57ded473c577719e6e551b7b1f27 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/4e6e07ce0197aecfb6c4a62862acc93b3efedeb7
- git.kernel.org/stable/c/6245cce711e2cdb2cc75c0bb8632952e36f8c972
- git.kernel.org/stable/c/79197c6007f2afbfd7bcf5b9b80ccabf8483d774
- git.kernel.org/stable/c/c7d393267c497502fa737607f435f05dfe6e3d9b
- git.kernel.org/stable/c/ca9388fba50dac2eb71c13702b7022a801bef90e
- git.kernel.org/stable/c/d138f73ffb0c57ded473c577719e6e551b7b1f27
Vendor advisories and official records. Exploit/PoC links are deliberately left out.