{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54058 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54058 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-2023-54058 and fix it if it is affected.\n\nWhat it is: CVE-2023-54058 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-2023-54058 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-54058/ (Markdown: https://insights.sbomify.com/CVE-2023-54058/index.md)","id":"CVE-2023-54058","markdown":"https://insights.sbomify.com/CVE-2023-54058/index.md","name":"CVE-2023-54058","record":{"aliases":["BELL-CVE-2023-54058","DEBIAN-CVE-2023-54058","GHSA-chjw-9fmq-6p9g","UBUNTU-CVE-2023-54058"],"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 local attacker can cause a kernel crash by unloading an ARM FFA driver that lacks a remove callback, leading to a null pointer dereference.","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\nfirmware: arm_ffa: Check if ffa_driver remove is present before executing\n\nCurrently ffa_drv-\u003eremove() is called unconditionally from\nffa_device_remove(). Since the driver registration doesn't check for it\nand allows it to be registered without .remove callback, we need to check\nfor the presence of it before executing it from ffa_device_remove() to\nabove a NULL pointer dereference like the one below:\n\n  | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n  | Mem abort info:\n  |   ESR = 0x0000000086000004\n  |   EC = 0x21: IABT (current EL), IL = 32 bits\n  |   SET = 0, FnV = 0\n  |   EA = 0, S1PTW = 0\n  |   FSC = 0x04: level 0 translation fault\n  | user pgtable: 4k pages, 48-bit VAs, pgdp=0000000881cc8000\n  | [0000000000000000] pgd=0000000000000000, p4d=0000000000000000\n  | Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP\n  | CPU: 3 PID: 130 Comm: rmmod Not tainted 6.3.0-rc7 #6\n  | Hardware name: FVP Base RevC (DT)\n  | pstate: 63402809 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=-c)\n  | pc : 0x0\n  | lr : ffa_device_remove+0x20/0x2c\n  | Call trace:\n  |  0x0\n  |  device_release_driver_internal+0x16c/0x260\n  |  driver_detach+0x90/0xd0\n  |  bus_remove_driver+0xdc/0x11c\n  |  driver_unregister+0x30/0x54\n  |  ffa_driver_unregister+0x14/0x20\n  |  cleanup_module+0x18/0xeec\n  |  __arm64_sys_delete_module+0x234/0x378\n  |  invoke_syscall+0x40/0x108\n  |  el0_svc_common+0xb4/0xf0\n  |  do_el0_svc+0x30/0xa4\n  |  el0_svc+0x2c/0x7c\n  |  el0t_64_sync_handler+0x84/0xf0\n  |  el0t_64_sync+0x190/0x194","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":"firmware: arm_ffa: Check if ffa_driver remove is present before executing","id":"CVE-2023-54058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"soc: mediatek: mtk-svs: Enable the IRQ later","id":"CVE-2023-54059"},"packages":[],"prev":{"headline":"iommu/amd: Add a length limitation for the ivrs_acpihid command-line parameter","id":"CVE-2023-54057"},"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 local attacker can cause a kernel crash by unloading an ARM FFA driver that lacks a remove callback, leading to a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2023-54058/"}