{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68168 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68168 is a high-severity vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68168 and fix it if it is affected.\n\nWhat it is: CVE-2025-68168 is a high-severity vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68168 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68168/ (Markdown: https://insights.sbomify.com/CVE-2025-68168/index.md)","id":"CVE-2025-68168","markdown":"https://insights.sbomify.com/CVE-2025-68168/index.md","name":"CVE-2025-68168","record":{"aliases":["BELL-CVE-2025-68168","DEBIAN-CVE-2025-68168","GHSA-35pf-3h4j-jg2m","ROOT-OS-UBUNTU-2204-CVE-2025-68168","ROOT-OS-UBUNTU-2404-CVE-2025-68168","UBUNTU-CVE-2025-68168"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel JFS","requires_auth":"low_privilege","summary":"An uninitialized waitqueue in the JFS transaction manager causes a system crash when mounting read-only filesystems, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\njfs: fix uninitialized waitqueue in transaction manager\n\nThe transaction manager initialization in txInit() was not properly\ninitializing TxBlock[0].waitor waitqueue, causing a crash when\ntxEnd(0) is called on read-only filesystems.\n\nWhen a filesystem is mounted read-only, txBegin() returns tid=0 to\nindicate no transaction. However, txEnd(0) still gets called and\ntries to access TxBlock[0].waitor via tid_to_tblock(0), but this\nwaitqueue was never initialized because the initialization loop\nstarted at index 1 instead of 0.\n\nThis causes a 'non-static key' lockdep warning and system crash:\n  INFO: trying to register non-static key in txEnd\n\nFix by ensuring all transaction blocks including TxBlock[0] have\ntheir waitqueues properly initialized during txInit().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"jfs: fix uninitialized waitqueue in transaction manager","id":"CVE-2025-68168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"netpoll: Fix deadlock in memory allocation under spinlock","id":"CVE-2025-68169"},"packages":[],"prev":{"headline":"gpiolib: fix invalid pointer access in debugfs","id":"CVE-2025-68167"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"An uninitialized waitqueue in the JFS transaction manager causes a system crash when mounting read-only filesystems, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-68168/"}