{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53708 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53708 is a memory corruption vulnerability in Linux, published on 22 Oct 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-53708 and fix it if it is affected.\n\nWhat it is: CVE-2023-53708 is a memory corruption vulnerability in Linux, published on 22 Oct 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-53708 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-53708/ (Markdown: https://insights.sbomify.com/CVE-2023-53708/index.md)","id":"CVE-2023-53708","markdown":"https://insights.sbomify.com/CVE-2023-53708/index.md","name":"CVE-2023-53708","record":{"aliases":["BELL-CVE-2023-53708","DEBIAN-CVE-2023-53708","GHSA-2f48-8mh4-9hm3","UBUNTU-CVE-2023-53708"],"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 memory leak in the Linux kernel's ACPI s2idle handler allows local attackers to cause denial of service via crafted firmware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects\n\nIf a badly constructed firmware includes multiple `ACPI_TYPE_PACKAGE`\nobjects while evaluating the AMD LPS0 _DSM, there will be a memory\nleak.  Explicitly guard against this.","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":"ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects","id":"CVE-2023-53708","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"ring-buffer: Handle race between rb_move_tail and rb_check_pages","id":"CVE-2023-53709"},"packages":[],"prev":{"headline":"drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1","id":"CVE-2023-53707"},"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 memory leak in the Linux kernel's ACPI s2idle handler allows local attackers to cause denial of service via crafted firmware.","url":"https://insights.sbomify.com/CVE-2023-53708/"}