{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89587 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89587 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89587 and fix it if it is affected.\n\nWhat it is: CVE-2026-89587 is a high-severity memory corruption vulnerability in Linux, published on 11 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-89587 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-89587/ (Markdown: https://insights.sbomify.com/CVE-2026-89587/index.md)","id":"CVE-2026-89587","markdown":"https://insights.sbomify.com/CVE-2026-89587/index.md","name":"CVE-2026-89587","record":{"aliases":["AZL-100392","BELL-CVE-2026-89587","DEBIAN-CVE-2026-89587","GHSA-2qcc-62m3-pg4c","UBUNTU-CVE-2026-89587"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A stack buffer overflow in the Linux kernel ACPI PFR update driver allows attackers with firmware control to execute arbitrary code or escalate privileges.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nACPI: pfr_update: fix stack buffer overflow in query_capability()\n\nquery_capability() copies four ACPI buffer objects returned by the\nfirmware _DSM into fixed-size u8[16] fields in struct\npfru_update_cap_info using memcpy with the firmware-supplied length:\n\n  memcpy(\u0026cap_hdr-\u003ecode_type,\n         elements[CAP_CODE_TYPE_IDX].buffer.pointer,\n         elements[CAP_CODE_TYPE_IDX].buffer.length);\n\nThe same pattern repeats for drv_type, platform_id, and oem_id.\nIf the firmware returns buffer.length \u003e 16 for any of these fields,\nmemcpy writes past the destination array.\n\nstruct pfru_update_cap_info is stack-allocated in pfru_ioctl().\n\nConfirmed with KASAN on 7.2-rc6: three stack-out-of-bounds reports\nare generated when a DSM returns 64-byte buffers, with writes reaching\n44 bytes past the end of cap_hdr's [64, 156) frame window into\nadjacent stack redzones.\n\nIntroduce a helper pointer to out_obj-\u003epackage.elements and use it\nto validate each buffer length against its destination field size\nbefore copying, returning -EINVAL if the firmware supplies an\noversized buffer.","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: pfr_update: fix stack buffer overflow in query_capability()","id":"CVE-2026-89587","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"ACPI: APEI: GHES: fix ARM section length accounting after header","id":"CVE-2026-89588"},"packages":[],"prev":{"headline":"ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes","id":"CVE-2026-89586"},"products":["Linux"],"published":"2026-09-11","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-19","vendors":["Linux"]},"summary":"A stack buffer overflow in the Linux kernel ACPI PFR update driver allows attackers with firmware control to execute arbitrary code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-89587/"}