VulnerabilityPublished 5 Jan 2026Updated 31 Jul 2026

CVE-2025-68757: Linux kernel · drm/vgem-fence: Fix potential deadlock on release

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 5.15.0-1103.110~20.04.1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.15.0-1103.110~20.04.1, 5.15.0-1110.119~20.04.1, 5.15.0-1103.112~20.04.1 +70

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Ubuntu 25.10linux`pkg:deb/ubuntu/linux@6.17.0-19.19?arch=source&distro=questing`Other threats	Affected <6.17.0-19.19	Fixed in 6.17.0-19.19
Ubuntu 25.10linux-aws`pkg:deb/ubuntu/linux-aws@6.17.0-1009.9?arch=source&distro=questing`Other threats	Affected <6.17.0-1009.9	Fixed in 6.17.0-1009.9
Ubuntu 25.10linux-azure`pkg:deb/ubuntu/linux-azure@6.17.0-1010.10?arch=source&distro=questing`Other threats	Affected <6.17.0-1010.10	Fixed in 6.17.0-1010.10
Ubuntu 25.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde@6.17.0-1017.17?arch=source&distro=questing`Other threats	Affected 6.17.0-1003.3 – 6.17.0-1017.17 10 affected builds	Fixed in–
Ubuntu 25.10linux-gcp`pkg:deb/ubuntu/linux-gcp@6.17.0-1009.9?arch=source&distro=questing`Other threats	Affected <6.17.0-1009.9	Fixed in 6.17.0-1009.9
Ubuntu 25.10linux-oracle`pkg:deb/ubuntu/linux-oracle@6.17.0-1009.9?arch=source&distro=questing`Other threats	Affected <6.17.0-1009.9	Fixed in 6.17.0-1009.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied to affected Linux Azure kernel versions. The vendor advisory from Ubuntu confirms that this issue is fixed in updated kernel packages. Users should update to the fixed kernel versions to mitigate this vulnerability.

Description

A potential deadlock vulnerability was identified and fixed in the Linux kernel's drm/vgem-fence subsystem. The issue involved unsafe locking scenarios related to timer deletion in IRQ context without proper safeguards, which could cause system instability. The vulnerability was demonstrated during specific Intel DRM continuous integration tests. Multiple Linux Azure kernel versions prior to specific 5.15.x updates are affected. A patch is available to address this issue.

Impact

This vulnerability could cause a deadlock in the kernel, leading to system instability or hangs. It does not directly enable privilege escalation or code execution but affects kernel reliability and availability under certain conditions.

Summary

The Linux kernel's drm/vgem-fence component had a potential deadlock vulnerability caused by improper handling of a timer that expires a vgem fence after 10 seconds. The timer was released using timer_delete_sync() from fence->ops.release() during the last dma_fence_put() call. In some cases, this release could occur in IRQ context without the TIMER_IRQSAFE flag, leading to unsafe locking and potential deadlocks. This was observed in Intel DRM CI trybot tests involving new IGT subtests. The issue has been resolved in patched kernel versions.

GCVE source: db.gcve.eu
OSV ID: UBUNTU-CVE-2025-68757
Osv Schema Version: 1.7.0
Ecosystems: Ubuntu:Pro:14.04:LTS, Ubuntu:Pro:16.04:LTS, Ubuntu:16.04:LTS, Ubuntu:Pro:18.04:LTS, Ubuntu:18.04:LTS, Ubuntu:Pro:FIPS-updates:18.04:LTS, Ubuntu:Pro:FIPS:18.04:LTS, Ubuntu:Pro:20.04:LTS, Ubuntu:20.04:LTS, Ubuntu:Pro:FIPS-updates:20.04:LTS, Ubuntu:Pro:FIPS:20.04:LTS, Ubuntu:22.04:LTS, Ubuntu:Nvidia-BlueField:22.04:LTS, Ubuntu:Pro:FIPS-preview:22.04:LTS, Ubuntu:Pro:FIPS-updates:22.04:LTS, Ubuntu:Pro:Realtime:22.04:LTS, Ubuntu:24.04:LTS, Ubuntu:Nvidia-BlueField:24.04:LTS, Ubuntu:Pro:FIPS-updates:24.04:LTS, Ubuntu:Pro:Realtime:24.04:LTS, Ubuntu:25.10

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Sep 2026, 12:35 UTC

Technical details

References

Community reviews

Related threats