{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98528 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98528 is a 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-98528 and fix it if it is affected.\n\nWhat it is: CVE-2026-98528 is a 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-98528 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-98528/ (Markdown: https://insights.sbomify.com/CVE-2026-98528/index.md)","id":"CVE-2026-98528","markdown":"https://insights.sbomify.com/CVE-2026-98528/index.md","name":"CVE-2026-98528","record":{"aliases":["BELL-CVE-2026-98528","DEBIAN-CVE-2026-98528","GHSA-2259-3wph-4x6g","UBUNTU-CVE-2026-98528"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel stack memory via a GPIO character device error path, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: cdev: fix kernel stack leak to user-space in error path\n\nIf we fail to acquire the GPIO chip guard in gpio_desc_to_lineinfo(), we\nreturn immediately before zeroing the info struct we'll end up passing\nto the user-space later in lineinfo_get_v1(). This may leak the kernel\nstack contents. Make gpio_desc_to_lineinfo() return int so that the\n-ENODEV returned on failure to acquire the guard can be propagated to\nthe callers.\n\nWhile not strictly necessary: move the memset() before trying to acquire\nthe SRCU read lock too for good measure.","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: cdev: fix kernel stack leak to user-space in error path","id":"CVE-2026-98528","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"gpio: arizona: Fix runtime PM leak in arizona_gpio_direction_out()","id":"CVE-2026-98529"},"packages":[],"prev":{"headline":"gpio: zynq: fix runtime PM leak on request error path","id":"CVE-2026-98527"},"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 read uninitialized kernel stack memory via a GPIO character device error path, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-98528/"}