{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53694 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53694 is a vulnerability in Linux, published on 22 Oct 2025."},"fix_prompt":"Check this codebase for CVE-2023-53694 and fix it if it is affected.\n\nWhat it is: CVE-2023-53694 is a vulnerability in Linux, published on 22 Oct 2025. \nExploitation: There is no known exploitation of CVE-2023-53694 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-53694/ (Markdown: https://insights.sbomify.com/CVE-2023-53694/index.md)","id":"CVE-2023-53694","markdown":"https://insights.sbomify.com/CVE-2023-53694/index.md","name":"CVE-2023-53694","record":{"aliases":["BELL-CVE-2023-53694","DEBIAN-CVE-2023-53694","GHSA-65c4-f76q-3c6g","ROOT-OS-UBUNTU-2204-CVE-2023-53694","UBUNTU-CVE-2023-53694"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the RISC-V Linux kernel ftrace implementation can cause a system panic if preemption occurs during code patching.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nriscv: ftrace: Fixup panic by disabling preemption\n\nIn RISCV, we must use an AUIPC + JALR pair to encode an immediate,\nforming a jump that jumps to an address over 4K. This may cause errors\nif we want to enable kernel preemption and remove dependency from\npatching code with stop_machine(). For example, if a task was switched\nout on auipc. And, if we changed the ftrace function before it was\nswitched back, then it would jump to an address that has updated 11:0\nbits mixing with previous XLEN:12 part.\n\np: patched area performed by dynamic ftrace\nftrace_prologue:\np|      REG_S   ra, -SZREG(sp)\np|      auipc   ra, 0x? ------------\u003e preempted\n\t\t\t\t\t...\n\t\t\t\tchange ftrace function\n\t\t\t\t\t...\np|      jalr    -?(ra) \u003c------------- switched back\np|      REG_L   ra, -SZREG(sp)\nfunc:\n\txxx\n\tret","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":"riscv: ftrace: Fixup panic by disabling preemption","id":"CVE-2023-53694","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"udf: Detect system inodes linked into directory hierarchy","id":"CVE-2023-53695"},"packages":[],"prev":{"headline":"USB: gadget: Fix the memory leak in raw_gadget driver","id":"CVE-2023-53693"},"products":["Linux"],"published":"2025-10-22","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-11","vendors":["Linux"]},"summary":"A race condition in the RISC-V Linux kernel ftrace implementation can cause a system panic if preemption occurs during code patching.","url":"https://insights.sbomify.com/CVE-2023-53694/"}