{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97451 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97451 is a high-severity vulnerability in Linux, published on 24 Sep 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-97451 and fix it if it is affected.\n\nWhat it is: CVE-2026-97451 is a high-severity vulnerability in Linux, published on 24 Sep 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-97451 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-97451/ (Markdown: https://insights.sbomify.com/CVE-2026-97451/index.md)","id":"CVE-2026-97451","markdown":"https://insights.sbomify.com/CVE-2026-97451/index.md","name":"CVE-2026-97451","record":{"aliases":["AZL-103952","BELL-CVE-2026-97451","DEBIAN-CVE-2026-97451","GHSA-w3m4-cvqw-754j","UBUNTU-CVE-2026-97451"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel ACPICA","requires_auth":"none","summary":"An integer overflow in the Linux kernel's ACPICA component allows negative size parameters in memcpy, potentially leading to memory corruption or crashes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op)\n\nAdd overflow check for Index + Length to prevent integer overflow\nwhen calculating the truncation length. This prevents negative\nsize parameter being passed to memcpy().","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":"ACPICA: Fix integer overflow in acpi_ex_opcode_3A_1T_1R() (mid_op)","id":"CVE-2026-97451","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ACPICA: Prevent adding invalid references","id":"CVE-2026-97452"},"packages":[],"prev":{"headline":"ACPICA: validate handler object type in two places","id":"CVE-2026-97450"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-03","vendors":["Linux"]},"summary":"An integer overflow in the Linux kernel's ACPICA component allows negative size parameters in memcpy, potentially leading to memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2026-97451/"}