{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53818 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53818 is a denial of service vulnerability in Linux, published on 9 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-53818 and fix it if it is affected.\n\nWhat it is: CVE-2023-53818 is a denial of service vulnerability in Linux, published on 9 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-53818 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-53818/ (Markdown: https://insights.sbomify.com/CVE-2023-53818/index.md)","id":"CVE-2023-53818","markdown":"https://insights.sbomify.com/CVE-2023-53818/index.md","name":"CVE-2023-53818","record":{"aliases":["BELL-CVE-2023-53818","DEBIAN-CVE-2023-53818","GHSA-qw6q-8fw7-j594","UBUNTU-CVE-2023-53818"],"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 refcount leak in the ARM Zynq early SLCR initialization can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nARM: zynq: Fix refcount leak in zynq_early_slcr_init\n\nof_find_compatible_node() returns a node pointer with refcount incremented,\nwe should use of_node_put() on error path.\nAdd missing of_node_put() to avoid refcount leak.","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":"ARM: zynq: Fix refcount leak in zynq_early_slcr_init","id":"CVE-2023-53818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":8,"next":{"headline":"amdgpu: validate offset_in_bo of drm_amdgpu_gem_va","id":"CVE-2023-53819"},"packages":[],"prev":{"headline":"crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()","id":"CVE-2023-53817"},"products":["Linux"],"published":"2025-12-09","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 refcount leak in the ARM Zynq early SLCR initialization can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2023-53818/"}