{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-23043 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23043 is a vulnerability in Linux, published on 4 Feb 2026. 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-2026-23043 and fix it if it is affected.\n\nWhat it is: CVE-2026-23043 is a vulnerability in Linux, published on 4 Feb 2026. 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-2026-23043 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-2026-23043/ (Markdown: https://insights.sbomify.com/CVE-2026-23043/index.md)","id":"CVE-2026-23043","markdown":"https://insights.sbomify.com/CVE-2026-23043/index.md","name":"CVE-2026-23043","record":{"aliases":["BELL-CVE-2026-23043","DEBIAN-CVE-2026-23043","GHSA-79jf-89ph-wp26","UBUNTU-CVE-2026-23043"],"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 local attacker can cause a kernel crash via a NULL pointer dereference in the btrfs filesystem log replay abort path.","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\nbtrfs: fix NULL pointer dereference in do_abort_log_replay()\n\nCoverity reported a NULL pointer dereference issue (CID 1666756) in\ndo_abort_log_replay(). When btrfs_alloc_path() fails in\nreplay_one_buffer(), wc-\u003esubvol_path is NULL, but btrfs_abort_log_replay()\ncalls do_abort_log_replay() which unconditionally dereferences\nwc-\u003esubvol_path when attempting to print debug information. Fix this by\nadding a NULL check before dereferencing wc-\u003esubvol_path in\ndo_abort_log_replay().","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":"btrfs: fix NULL pointer dereference in do_abort_log_replay()","id":"CVE-2026-23043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"PM: hibernate: Fix crash when freeing invalid crypto compressor","id":"CVE-2026-23044"},"packages":[],"prev":{"headline":"idpf: fix aux device unplugging when rdma is not supported by vport","id":"CVE-2026-23042"},"products":["Linux"],"published":"2026-02-04","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 local attacker can cause a kernel crash via a NULL pointer dereference in the btrfs filesystem log replay abort path.","url":"https://insights.sbomify.com/CVE-2026-23043/"}