{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81015 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-81015 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-81015 and fix it if it is affected.\n\nWhat it is: CVE-2026-81015 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-81015 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-81015/ (Markdown: https://insights.sbomify.com/CVE-2026-81015/index.md)","id":"CVE-2026-81015","markdown":"https://insights.sbomify.com/CVE-2026-81015/index.md","name":"CVE-2026-81015","record":{"aliases":["BELL-CVE-2026-81015","DEBIAN-CVE-2026-81015","GHSA-4m25-x3hr-48wm","UBUNTU-CVE-2026-81015"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A kernel bug in the AMD PMC driver causes memory corruption and system crashes when initialization fails, leading to denial of service.","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\nplatform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails\n\namd_pmc_probe() registers the LPS0 s2idle handler with\nacpi_register_lps0_dev() and creates the driver's debugfs directory before\ncalling amd_stb_s2d_init(), which is the last step in probe that can fail.\n\nWhen amd_stb_s2d_init() fails (for example the S2D telemetry region cannot\nbe ioremapped on a long-running system, or the SMU rejects the S2D setup)\nthe error path only calls pci_dev_put() and returns.  This leaves\namd_pmc_s2idle_dev_ops on the global lps0_s2idle_devops_head list and leaks\nthe debugfs directory, while the devm-managed resources backing the handler\nare torn down.\n\nReloading the module then walks the corrupted list in\nacpi_register_lps0_dev() and hits:\n\n  list_add corruption. next-\u003eprev should be prev, but was NULL.\n  kernel BUG at lib/list_debug.c:29!\n   acpi_register_lps0_dev+0x44/0x80\n   amd_pmc_probe+0x224/0x380 [amd_pmc]\n   platform_probe+0x67/0x90\n\nEven without a reload, the stale registration means the next s2idle\ntransition calls into torn-down driver state.\n\nUnwind the debugfs directory and the LPS0 registration on the\namd_stb_s2d_init() error path.  acpi_unregister_lps0_dev() is safe to call\nunconditionally here: it is guarded on the same conditions as\nacpi_register_lps0_dev(), which is exactly what amd_pmc_remove() already\nrelies on.","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":"platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails","id":"CVE-2026-81015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"platform/x86/amd/pmc: Propagate SMU errors and validate S2D address","id":"CVE-2026-81016"},"packages":[],"prev":{"headline":"platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store()","id":"CVE-2026-81014"},"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 kernel bug in the AMD PMC driver causes memory corruption and system crashes when initialization fails, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-81015/"}