In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager… (CVE-2025-68168)
A vulnerability in the Linux kernel's JFS transaction manager was fixed by properly initializing the waitqueue for TxBlock[0]. The issue caused a system crash when txEnd(0) was called on read-only filesystems due to an uninitialized waitqueue. This led to a lockdep warning and crash. The fix ensures all transaction blocks, including TxBlock[0], have their waitqueues initialized during txInit().
AI Analysis
Technical Summary
The Linux kernel's JFS transaction manager had a flaw where the waitqueue for TxBlock[0] was not initialized because the initialization loop started at index 1 instead of 0. When a filesystem is mounted read-only, txBegin() returns tid=0 indicating no transaction, but txEnd(0) is still called and attempts to access the uninitialized TxBlock[0].waitor waitqueue, causing a 'non-static key' lockdep warning and system crash. The vulnerability was resolved by initializing the waitqueue for all transaction blocks, including TxBlock[0], during txInit().
Potential Impact
This vulnerability can cause a system crash when operating on read-only filesystems using the JFS transaction manager, leading to denial of service. The CVSS vector indicates high impact on confidentiality, integrity, and availability, but no known exploits are reported in the wild.
Mitigation Recommendations
A fix is available that properly initializes the waitqueue for TxBlock[0] during transaction manager initialization. Users should apply the official Linux kernel patch that addresses this issue. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager… (CVE-2025-68168)
Description
A vulnerability in the Linux kernel's JFS transaction manager was fixed by properly initializing the waitqueue for TxBlock[0]. The issue caused a system crash when txEnd(0) was called on read-only filesystems due to an uninitialized waitqueue. This led to a lockdep warning and crash. The fix ensures all transaction blocks, including TxBlock[0], have their waitqueues initialized during txInit().
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's JFS transaction manager had a flaw where the waitqueue for TxBlock[0] was not initialized because the initialization loop started at index 1 instead of 0. When a filesystem is mounted read-only, txBegin() returns tid=0 indicating no transaction, but txEnd(0) is still called and attempts to access the uninitialized TxBlock[0].waitor waitqueue, causing a 'non-static key' lockdep warning and system crash. The vulnerability was resolved by initializing the waitqueue for all transaction blocks, including TxBlock[0], during txInit().
Potential Impact
This vulnerability can cause a system crash when operating on read-only filesystems using the JFS transaction manager, leading to denial of service. The CVSS vector indicates high impact on confidentiality, integrity, and availability, but no known exploits are reported in the wild.
Mitigation Recommendations
A fix is available that properly initializes the waitqueue for TxBlock[0] during transaction manager initialization. Users should apply the official Linux kernel patch that addresses this issue. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-35pf-3h4j-jg2m
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68168"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d39c2644c7f8478924
Added to database: 07/30/2026, 15:50:43 UTC
Last enriched: 07/30/2026, 18:08:46 UTC
Last updated: 09/10/2026, 19:26:55 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.