CVE-2026-98528
Description
A flaw was found in the Linux kernel's GPIO (General Purpose Input/Output) character device interface. This vulnerability allows a local user to cause an information disclosure of sensitive kernel stack data. When an error occurs while querying GPIO line details, the kernel fails to clear the data structure before passing it back to user space, leaking uninitialized kernel memory contents.
Statement
This vulnerability is assessed as having a Low impact because exploitation is restricted to authenticated local users who have access to GPIO character device nodes, and the defect only exposes uninitialized kernel stack memory without enabling privilege escalation or system crashes. In standard enterprise deployments, GPIO controllers are rarely present and access to corresponding device interfaces is limited to privileged accounts by default. Furthermore, Red Hat Enterprise Linux versions 8 and 9 are unaffected as they do not contain the vulnerable code path.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 3.3 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | Low | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory; Read Application Data
When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability
The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.
Other
Technical Impact: Unexpected State; Varies by Context
The consequences vary depending on the type of resource and how it is used within the product.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
