CVE-2025-68168 Details
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().
A vulnerability in the Linux kernel's JFS (Journaled File System) transaction manager has been identified, where the initialization of the waitqueue for transaction block 0 was not properly handled. This issue can lead to a system crash when the function txEnd(0) is called on read-only filesystems. The problem arises because, on read-only filesystems, the function txBegin() returns a transaction ID of 0, indicating that no transaction is active. However, txEnd(0) is still invoked, attempting to access the waitqueue for transaction block 0. Since the initialization process for the transaction blocks started at index 1 instead of 0, the waitqueue for block 0 was never initialized. This oversight triggers a lockdep warning about a non-static key and results in a system crash.
Users can apply the available patch to fix this vulnerability. The patch is included in the official Linux kernel repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 16, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/038861414ab383b41dd35abbf9ff0ef715592d53 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/2a9575a372182ca075070b3cd77490dcf0c951e7 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/300b072df72694ea330c4c673c035253e07827b8 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/8cae9cf23e0bd424ac904e753639a587543ce03a | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a2aa97cde9857f881920635a2e3d3b11769619c5 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/cbf2f527ae4ca7c7dabce42e85e8deb58588a37e | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d2dd7ca05a11685c314e62802a55e8d67a90e974 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | New CVE Received | kernel.org |
Volerion