jfs: fix uninitialized waitqueue in transaction manager
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 95e2b352c03b0a86c5717ba1d24ea20969abcacc · < cbf2f527ae4ca7c7dabce42e85e8deb58588a37e| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel’s JFS transaction manager fails to initialize a waitqueue used by read-only filesystems. When txEnd(0) accesses it, the system can crash. The input does not establish how an attacker could trigger this or whether authentication or user interaction is required.
Anyone running the Linux kernel with JFS should check their kernel version; affected versions are not specified.