Review reviewHigh

CVE-2025-68168

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. Thi...

CVSS
7.8
EPSS
0.13%
3.34% percentile
CISA KEV
Not listed
Published
2025.12.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

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. Thi...

Affected product and versions

Product
Linux
Affected versions
>= 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, >= 6.5
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

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