{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98527 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98527 is a denial of service vulnerability in Linux, published on 18 Oct 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-98527 and fix it if it is affected.\n\nWhat it is: CVE-2026-98527 is a denial of service vulnerability in Linux, published on 18 Oct 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-98527 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-98527/ (Markdown: https://insights.sbomify.com/CVE-2026-98527/index.md)","id":"CVE-2026-98527","markdown":"https://insights.sbomify.com/CVE-2026-98527/index.md","name":"CVE-2026-98527","record":{"aliases":["AZL-108981","BELL-CVE-2026-98527","DEBIAN-CVE-2026-98527","GHSA-xv89-vpfw-p3mv","UBUNTU-CVE-2026-98527"],"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":"none","summary":"A local attacker can trigger a runtime PM leak in the Zynq GPIO driver, preventing the controller from suspending and keeping its clock enabled.","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\ngpio: zynq: fix runtime PM leak on request error path\n\npm_runtime_get_sync() leaves the usage counter incremented even when it\nfails, and zynq_gpio_request() returns the error without dropping it.\n\ngpiolib does not call -\u003efree() when -\u003erequest() fails, so zynq_gpio_free(),\nwhich holds the only matching pm_runtime_put(), never runs. The reference\nis leaked and the controller can no longer runtime-suspend, so its clock\nstays enabled.\n\nSwitch to pm_runtime_resume_and_get(), which only increments the usage\ncounter on success.","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":"gpio: zynq: fix runtime PM leak on request error path","id":"CVE-2026-98527","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"gpio: cdev: fix kernel stack leak to user-space in error path","id":"CVE-2026-98528"},"packages":[],"prev":{"headline":"llc: reserve device headroom for allocated frames","id":"CVE-2026-98526"},"products":["Linux"],"published":"2026-10-18","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-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a runtime PM leak in the Zynq GPIO driver, preventing the controller from suspending and keeping its clock enabled.","url":"https://insights.sbomify.com/CVE-2026-98527/"}