{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68357 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68357 is a vulnerability in Linux, published on 24 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-68357 and fix it if it is affected.\n\nWhat it is: CVE-2025-68357 is a vulnerability in Linux, published on 24 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-68357 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-68357/ (Markdown: https://insights.sbomify.com/CVE-2025-68357/index.md)","id":"CVE-2025-68357","markdown":"https://insights.sbomify.com/CVE-2025-68357/index.md","name":"CVE-2025-68357","record":{"aliases":["AZL-73078","BELL-CVE-2025-68357","DEBIAN-CVE-2025-68357","GHSA-6998-95jp-6xx2","ROOT-OS-DEBIAN-13-CVE-2025-68357","UBUNTU-CVE-2025-68357"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing workqueue allocation for async reads in the Linux kernel iomap subsystem can lead to a null pointer dereference and system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niomap: allocate s_dio_done_wq for async reads as well\n\nSince commit 222f2c7c6d14 (\"iomap: always run error completions in user\ncontext\"), read error completions are deferred to s_dio_done_wq.  This\nmeans the workqueue also needs to be allocated for async reads.","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":"iomap: allocate s_dio_done_wq for async reads as well","id":"CVE-2025-68357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"btrfs: fix racy bitfield write in btrfs_clear_space_info_full()","id":"CVE-2025-68358"},"packages":[],"prev":{"headline":"gfs2: Prevent recursive memory reclaim","id":"CVE-2025-68356"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A missing workqueue allocation for async reads in the Linux kernel iomap subsystem can lead to a null pointer dereference and system crash.","url":"https://insights.sbomify.com/CVE-2025-68357/"}