{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54152 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54152 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-54152 and fix it if it is affected.\n\nWhat it is: CVE-2023-54152 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-54152 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-54152/ (Markdown: https://insights.sbomify.com/CVE-2023-54152/index.md)","id":"CVE-2023-54152","markdown":"https://insights.sbomify.com/CVE-2023-54152/index.md","name":"CVE-2023-54152","record":{"aliases":["BELL-CVE-2023-54152","DEBIAN-CVE-2023-54152","GHSA-hxpg-6jhj-qw4q","UBUNTU-CVE-2023-54152"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel CAN","requires_auth":"none","summary":"A race condition in the Linux kernel CAN J1939 protocol can cause a deadlock, leading to denial of service.","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\ncan: j1939: prevent deadlock by moving j1939_sk_errqueue()\n\nThis commit addresses a deadlock situation that can occur in certain\nscenarios, such as when running data TP/ETP transfer and subscribing to\nthe error queue while receiving a net down event. The deadlock involves\nlocks in the following order:\n\n3\n  j1939_session_list_lock -\u003e  active_session_list_lock\n  j1939_session_activate\n  ...\n  j1939_sk_queue_activate_next -\u003e sk_session_queue_lock\n  ...\n  j1939_xtp_rx_eoma_one\n\n2\n  j1939_sk_queue_drop_all  -\u003e  sk_session_queue_lock\n  ...\n  j1939_sk_netdev_event_netdown -\u003e j1939_socks_lock\n  j1939_netdev_notify\n\n1\n  j1939_sk_errqueue -\u003e j1939_socks_lock\n  __j1939_session_cancel -\u003e active_session_list_lock\n  j1939_tp_rxtimer\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(\u0026priv-\u003eactive_session_list_lock);\n                               lock(\u0026jsk-\u003esk_session_queue_lock);\n                               lock(\u0026priv-\u003eactive_session_list_lock);\n  lock(\u0026priv-\u003ej1939_socks_lock);\n\nThe solution implemented in this commit is to move the\nj1939_sk_errqueue() call out of the active_session_list_lock context,\nthus preventing the deadlock situation.","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":"can: j1939: prevent deadlock by moving j1939_sk_errqueue()","id":"CVE-2023-54152","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"ext4: turn quotas off if mount failed after enabling quotas","id":"CVE-2023-54153"},"packages":[],"prev":{"headline":"f2fs: Fix system crash due to lack of free space in LFS","id":"CVE-2023-54151"},"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-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel CAN J1939 protocol can cause a deadlock, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2023-54152/"}