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().
CVSS
7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
from 2a8807f9f511c64de0c7cc9900a1683e3d72a3e5 before d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64; from 5c094ca994824e038b6a97835ded4e5d1d808504 before 8cae9cf23e0bd424ac904e753639a587543ce03a; from 2febd5f81e4bfba61d9f374dcca628aff374cc56 before a2aa97cde9857f881920635a2e3d3b11769619c5; from aa7cdf487ab3fa47284daaccc3d7d5de01c6a84c before d2dd7ca05a11685c314e62802a55e8d67a90e974; 95e2b352c03b0a86c5717ba1d24ea20969abcacc builds before 2a9575a372182ca075070b3cd77490dcf0c951e7; from 95e2b352c03b0a86c5717ba1d24ea20969abcacc before cbf2f527ae4ca7c7dabce42e85e8deb58588a37e; from 95e2b352c03b0a86c5717ba1d24ea20969abcacc before 038861414ab383b41dd35abbf9ff0ef715592d53; from 95e2b352c03b0a86c5717ba1d24ea20969abcacc before 300b072df72694ea330c4c673c035253e07827b8; and 10 more ranges
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.