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-68168

7.8 · HIGH
Published Dec 16, 2025 EPSS 0.15% (5th pctl)

Overview

CVE-2025-68168 is a high-severity vulnerability. It was published on December 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical Description

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

jfs: fix uninitialized waitqueue in transaction manager

The transaction manager initialization in txInit() was not properly

initializing TxBlock[0].waitor waitqueue, causing a crash when

txEnd(0) is called on read-only filesystems.

When a filesystem is mounted read-only, txBegin() returns tid=0 to

indicate no transaction. However, txEnd(0) still gets called and

tries to access TxBlock[0].waitor via tid_to_tblock(0), but this

waitqueue was never initialized because the initialization loop

started at index 1 instead of 0.

This causes a 'non-static key' lockdep warning and system crash:

INFO: trying to register non-static key in txEnd

Fix by ensuring all transaction blocks including TxBlock[0] have

their waitqueues properly initialized during txInit().

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

CVE-2025-68168 is a high-severity vulnerability. It was published on December 16, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-68168?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-68168?

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

CyberStrike's AI-powered security agents can automatically detect CVE-2025-68168 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.