CVE-2025-68168: jfs: fix uninitialized waitqueue in transaction manager
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 038861414ab383b41dd35abbf9ff0ef715592d53, 2a9575a372182ca075070b3cd77490dcf0c951e7, 300b072df72694ea330c4c673c035253e07827b8.
Low priority for now. Upgrade to Linux Linux 038861414ab383b41dd35abbf9ff0ef715592d53, 2a9575a372182ca075070b3cd77490dcf0c951e7, 300b072df72694ea330c4c673c035253e07827b8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Dec 16, 2025
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- a88efca805bea93cea9187dfd00835aa7093bf1b, 97c1f26e4d4af55e8584e4646dd5c5fa7baf62c7, b0ed8ed0428ee96092da6fefa5cfacbe4abed701, 6.5affected
- 2a8807f9f511c64de0c7cc9900a1683e3d72a3e5 and later · before d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64affected · git
- 5c094ca994824e038b6a97835ded4e5d1d808504 and later · before 8cae9cf23e0bd424ac904e753639a587543ce03aaffected · git
- 2febd5f81e4bfba61d9f374dcca628aff374cc56 and later · before a2aa97cde9857f881920635a2e3d3b11769619c5affected · git
- aa7cdf487ab3fa47284daaccc3d7d5de01c6a84c and later · before d2dd7ca05a11685c314e62802a55e8d67a90e974affected · git
- 95e2b352c03b0a86c5717ba1d24ea20969abcacc and later · before 2a9575a372182ca075070b3cd77490dcf0c951e7affected · git
- 95e2b352c03b0a86c5717ba1d24ea20969abcacc and later · before cbf2f527ae4ca7c7dabce42e85e8deb58588a37eaffected · git
- 95e2b352c03b0a86c5717ba1d24ea20969abcacc and later · before 038861414ab383b41dd35abbf9ff0ef715592d53affected · git
- 95e2b352c03b0a86c5717ba1d24ea20969abcacc and later · before 300b072df72694ea330c4c673c035253e07827b8affected · git
- 5.4.255 and later · before 5.4.302affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.159-1 | 6.1.159-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.8-1 | 6.17.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40363Dec 16, 2025 · net: ipv6: fix field-spanning memcpy warning in AH output0Monitor
- ← EarlierCVE-2025-68167Dec 16, 2025 · gpiolib: fix invalid pointer access in debugfs31Monitor
- Later →CVE-2025-68169Dec 16, 2025 · netpoll: Fix deadlock in memory allocation under spinlock0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 038861414ab383b41dd35abbf9ff0ef715592d53 | Vendor (CNA) |
| Linux Linux | 2a9575a372182ca075070b3cd77490dcf0c951e7 | Vendor (CNA) |
| Linux Linux | 300b072df72694ea330c4c673c035253e07827b8 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10.247 | Vendor (CNA) |
| Linux Linux | 5.15.197 | Vendor (CNA) |
| Linux Linux | 5.4.302 | Vendor (CNA) |
| Linux Linux | 6.1.159 | Vendor (CNA) |
| Linux Linux | 6.5 | Vendor (CNA) |
| Linux Linux | 8cae9cf23e0bd424ac904e753639a587543ce03a | Vendor (CNA) |
| Linux Linux | a2aa97cde9857f881920635a2e3d3b11769619c5 | Vendor (CNA) |
| Linux Linux | cbf2f527ae4ca7c7dabce42e85e8deb58588a37e | Vendor (CNA) |
| Linux Linux | d2dd7ca05a11685c314e62802a55e8d67a90e974 | Vendor (CNA) |
| Linux Linux | d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64 | Vendor (CNA) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2a9575a372182ca075070b3cd77490dcf0c951e7
- git.kernel.org/stable/c/300b072df72694ea330c4c673c035253e07827b8
- git.kernel.org/stable/c/8cae9cf23e0bd424ac904e753639a587543ce03a
- git.kernel.org/stable/c/a2aa97cde9857f881920635a2e3d3b11769619c5
- git.kernel.org/stable/c/cbf2f527ae4ca7c7dabce42e85e8deb58588a37e
- git.kernel.org/stable/c/d2dd7ca05a11685c314e62802a55e8d67a90e974
- git.kernel.org/stable/c/d6af7fce2e162ac68e85d3a11eb6ac8c35b24b64
Vendor advisories and official records. Exploit/PoC links are deliberately left out.