Strix
26.1K

CVE-2025-68168

HIGHCVSS 7.8/10EPSS 0.18%

Last modified

CVE-2025-68168 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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().. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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().

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.18%

8.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2a8807f9f511c64de0c7cc9900a1683e3d72a3e5, < d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64; >= 5c094ca994824e038b6a97835ded4e5d1d808504, < 8cae9cf23e0bd424ac904e753639a587543ce03a; >= 2febd5f81e4bfba61d9f374dcca628aff374cc56, < a2aa97cde9857f881920635a2e3d3b11769619c5; >= aa7cdf487ab3fa47284daaccc3d7d5de01c6a84c, < d2dd7ca05a11685c314e62802a55e8d67a90e974; >= 95e2b352c03b0a86c5717ba1d24ea20969abcacc, < 2a9575a372182ca075070b3cd77490dcf0c951e7; >= 95e2b352c03b0a86c5717ba1d24ea20969abcacc, < cbf2f527ae4ca7c7dabce42e85e8deb58588a37e; >= 95e2b352c03b0a86c5717ba1d24ea20969abcacc, < 038861414ab383b41dd35abbf9ff0ef715592d53; >= 95e2b352c03b0a86c5717ba1d24ea20969abcacc, < 300b072df72694ea330c4c673c035253e07827b8; a88efca805bea93cea9187dfd00835aa7093bf1b; 97c1f26e4d4af55e8584e4646dd5c5fa7baf62c7; b0ed8ed0428ee96092da6fefa5cfacbe4abed701; >= 5.4.255, < 5.4.302; >= 5.10.192, < 5.10.247; >= 5.15.123, < 5.15.197; >= 6.1.42, < 6.1.159; >= 4.14.324, < 4.15; >= 4.19.293, < 4.20; >= 6.4.7, < 6.5
LinuxLinux6.5

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-68168?
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().
How severe is CVE-2025-68168?
CVE-2025-68168 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2025-68168?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-68168?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST