{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54068 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54068 is a high-severity 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-2023-54068 and fix it if it is affected.\n\nWhat it is: CVE-2023-54068 is a high-severity 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-2023-54068 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-2023-54068/ (Markdown: https://insights.sbomify.com/CVE-2023-54068/index.md)","id":"CVE-2023-54068","markdown":"https://insights.sbomify.com/CVE-2023-54068/index.md","name":"CVE-2023-54068","record":{"aliases":["BELL-CVE-2023-54068","DEBIAN-CVE-2023-54068","GHSA-jvpv-rvr9-2264","UBUNTU-CVE-2023-54068"],"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":"low_privilege","summary":"A race condition in the Linux kernel's f2fs filesystem can trigger a kernel BUG during concurrent file writes, causing a system crash.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nf2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages()\n\nBUG_ON() will be triggered when writing files concurrently,\nbecause the same page is writtenback multiple times.\n\n1597 void folio_end_writeback(struct folio *folio)\n1598 {\n\t\t......\n1618     if (!__folio_end_writeback(folio))\n1619         BUG();\n\t\t......\n1625 }\n\nkernel BUG at mm/filemap.c:1619!\nCall Trace:\n \u003cTASK\u003e\n f2fs_write_end_io+0x1a0/0x370\n blk_update_request+0x6c/0x410\n blk_mq_end_request+0x15/0x130\n blk_complete_reqs+0x3c/0x50\n __do_softirq+0xb8/0x29b\n ? sort_range+0x20/0x20\n run_ksoftirqd+0x19/0x20\n smpboot_thread_fn+0x10b/0x1d0\n kthread+0xde/0x110\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x22/0x30\n \u003c/TASK\u003e\n\nBelow is the concurrency scenario:\n\n[Process A]\t\t[Process B]\t\t[Process C]\nf2fs_write_raw_pages()\n  - redirty_page_for_writepage()\n  - unlock page()\n\t\t\tf2fs_do_write_data_page()\n\t\t\t  - lock_page()\n\t\t\t  - clear_page_dirty_for_io()\n\t\t\t  - set_page_writeback() [1st writeback]\n\t\t\t    .....\n\t\t\t    - unlock page()\n\n\t\t\t\t\t\tgeneric_perform_write()\n\t\t\t\t\t\t  - f2fs_write_begin()\n\t\t\t\t\t\t    - wait_for_stable_page()\n\n\t\t\t\t\t\t  - f2fs_write_end()\n\t\t\t\t\t\t    - set_page_dirty()\n\n  - lock_page()\n    - f2fs_do_write_data_page()\n      - set_page_writeback() [2st writeback]\n\nThis problem was introduced by the previous commit 7377e853967b (\"f2fs:\ncompress: fix potential deadlock of compress file\"). All pagelocks were\nreleased in f2fs_write_raw_pages(), but whether the page was\nin the writeback state was ignored in the subsequent writing process.\nLet's fix it by waiting for the page to writeback before writing.","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":"f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages()","id":"CVE-2023-54068","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow","id":"CVE-2023-54069"},"packages":[],"prev":{"headline":"btrfs: fix race when deleting free space root from the dirty cow roots list","id":"CVE-2023-54067"},"products":["Linux"],"published":"2025-12-24","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":"A race condition in the Linux kernel's f2fs filesystem can trigger a kernel BUG during concurrent file writes, causing a system crash.","url":"https://insights.sbomify.com/CVE-2023-54068/"}