---
id: CVE-2025-68168
title: |-
  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, c…
summary: |-
  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, c…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
published: '2025-12-16'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-68168'
references:
  - url: 'https://git.kernel.org/stable/c/038861414ab383b41dd35abbf9ff0ef715592d53'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2a9575a372182ca075070b3cd77490dcf0c951e7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/300b072df72694ea330c4c673c035253e07827b8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8cae9cf23e0bd424ac904e753639a587543ce03a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a2aa97cde9857f881920635a2e3d3b11769619c5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/cbf2f527ae4ca7c7dabce42e85e8deb58588a37e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d2dd7ca05a11685c314e62802a55e8d67a90e974'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00155
epssPercentile: 0.04122
ingestedAt: '2026-10-14T13:30:58.442Z'
---

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

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

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.