CVE-2025-68203

Inconsistent lock state via interrupt-unsafe fence locking

Published Dec 16, 2025 · Updated Dec 16, 2025

The withdrawn record described a locking defect in the Linux Kernel amdgpu userq fence driver during concurrent fence processing. The report said amdgpu_userq_fence_driver_process() acquired fence_list_lock in interrupt context without disabling interrupts, then reused the lock in process context. The kernel CNA rejected the CVE on January 2, 2026, so no active vulnerability record or attacker precondition remains.

CVSS severityUnavailable
Unscored
EPSS probabilityUnavailable
No score available in this record
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

The withdrawn record described a locking defect in the Linux Kernel amdgpu userq fence driver during concurrent fence processing. The report said amdgpu_userq_fence_driver_process() acquired fence_list_lock in interrupt context without disabling interrupts, then reused the lock in process context. The kernel CNA rejected the CVE on January 2, 2026, so no active vulnerability record or attacker precondition remains.

The record

CVE
CVE-2025-68203
Published
Dec 16, 2025
Updated
Dec 16, 2025
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Dec 16, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 16, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1ad70a06d7e91c378b346a3718c81abb50a74b74
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6623c5f9fd877868fba133b4ae4dab0052e82dad

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linux Kernelversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1ad70a06d7e91c378b346a3718c81abb50a74b74; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6623c5f9fd877868fba133b4ae4dab0052e82dad

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo