Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2025-68757

Published Jan 5, 2026

Overview

CVE-2025-68757 is a known-severity vulnerability. It was published on January 5, 2026.

Technical Description

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

drm/vgem-fence: Fix potential deadlock on release

A timer that expires a vgem fence automatically in 10 seconds is now

released with timer_delete_sync() from fence->ops.release() called on last

dma_fence_put(). In some scenarios, it can run in IRQ context, which is

not safe unless TIMER_IRQSAFE is used. One potentially risky scenario was

demonstrated in Intel DRM CI trybot, BAT run on machine bat-adlp-6, while

working on new IGT subtests syncobj_timeline@stress-* as user space

replacements of some problematic test cases of a dma-fence-chain selftest

[1].

[117.004338] ================================

[117.004340] WARNING: inconsistent lock state

[117.004342] 6.17.0-rc7-CI_DRM_17270-g7644974e648c+ #1 Tainted: G S U

[117.004346] --------------------------------

[117.004347] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.

[117.004349] swapper/0/0 [HC1[1]:SC1[1]:HE0:SE0] takes:

[117.004352] ffff888138f86aa8 ((&f

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.

References

Ref git.kernel.org/stable/c/1026d1b0bd55e1be7ba0f9e9b1c9f6e02448f25a Ref git.kernel.org/stable/c/1f0ca9d3e7c38a39f1f12377c24decf0bba46e54 Ref git.kernel.org/stable/c/338e388c0d80ffc04963b6b0ec702ffdfd2c4eba Ref git.kernel.org/stable/c/37289a18099fc7ce916933bd542926a7334791a3 Ref git.kernel.org/stable/c/489b2158aec92a3fc256d70992416869f86e16e0 Ref git.kernel.org/stable/c/4f335cb8fad69b2be5accf0ebac3a8b345915f4e Ref git.kernel.org/stable/c/78b4d6463e9e69e5103f98b367f8984ad12cdc6f Ref git.kernel.org/stable/c/9dc3c78d21e16f5af1a9c3d11b4bd5276f891fe0

Frequently Asked Questions

What is CVE-2025-68757?

CVE-2025-68757 is a known-severity vulnerability. It was published on January 5, 2026.

How severe is CVE-2025-68757?

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

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

CyberStrike's AI-powered security agents can automatically detect CVE-2025-68757 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.

How CyberStrike Helps

Autonomous Discovery

AI agents map your attack surface to find vulnerabilities like this one.
Continuous Pentesting

Automated penetration testing that runs continuously, not just quarterly.
Code Review

AI-driven PR review catches vulnerable dependencies before they ship.
HackBrowser

Browser-based exploitation validates findings with real proof-of-concept.
Browse by year 2026