CVE-2025-68168 — jfs: fix uninitialized waitqueue in transaction manager
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().
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 97c1f26e4d4af55e8584e4646dd5c5fa7baf62c7version 6.5≥ 6.4.7 and < 6.5≥ 4.19.293 and < 4.20≥ 4.14.324 and < 4.15≥ 6.1.42 and < 6.1.159≥ 5.15.123 and < 5.15.197≥ 5.10.192 and < 5.10.247 and 11 more≥ 5.4.255 and < 5.4.302version b0ed8ed0428ee96092da6fefa5cfacbe4abed701≥ 2a8807f9f511c64de0c7cc9900a1683e3d72a3e5 and < d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64version a88efca805bea93cea9187dfd00835aa7093bf1b≥ 95e2b352c03b0a86c5717ba1d24ea20969abcacc and < 300b072df72694ea330c4c673c035253e07827b8≥ 95e2b352c03b0a86c5717ba1d24ea20969abcacc and < 038861414ab383b41dd35abbf9ff0ef715592d53≥ 95e2b352c03b0a86c5717ba1d24ea20969abcacc and < cbf2f527ae4ca7c7dabce42e85e8deb58588a37e≥ 95e2b352c03b0a86c5717ba1d24ea20969abcacc and < 2a9575a372182ca075070b3cd77490dcf0c951e7≥ aa7cdf487ab3fa47284daaccc3d7d5de01c6a84c and < d2dd7ca05a11685c314e62802a55e8d67a90e974≥ 2febd5f81e4bfba61d9f374dcca628aff374cc56 and < a2aa97cde9857f881920635a2e3d3b11769619c5≥ 5c094ca994824e038b6a97835ded4e5d1d808504 and < 8cae9cf23e0bd424ac904e753639a587543ce03a |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.16%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
10 on the record
- git.kernel.org/stable/c/a2aa97cde9857f881920635a2e3d3b11769619c5
- git.kernel.org/stable/c/300b072df72694ea330c4c673c035253e07827b8
- git.kernel.org/stable/c/d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64
- git.kernel.org/stable/c/2a9575a372182ca075070b3cd77490dcf0c951e7
- git.kernel.org/stable/c/cbf2f527ae4ca7c7dabce42e85e8deb58588a37e
- nvd.nist.gov/vuln/detail/CVE-2025-68168
- git.kernel.org/stable/c/038861414ab383b41dd35abbf9ff0ef715592d53
- git.kernel.org/stable/c/d2dd7ca05a11685c314e62802a55e8d67a90e974
- github.com/advisories/GHSA-35pf-3h4j-jg2m
- git.kernel.org/stable/c/8cae9cf23e0bd424ac904e753639a587543ce03a
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-68168 is "jfs: fix uninitialized waitqueue in transaction manager", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.16% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.