Quick answers
- Is CVE-2026-98203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98203 being exploited in the wild.
- How severe is CVE-2026-98203?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel from 4.14 onwards (commit 4c3362f44980 and later).
- Is there a fix for CVE-2026-98203?
- A patch was published on 2026-09-25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98203 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98203?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The soc_button_array driver failed to validate that btns_desc->package.count is non-zero before dereferencing btns_desc->package.elements[0], creating a null pointer dereference or out-of-bounds access condition. The vulnerability exists in the soc_button_get_button_info() function when parsing ACPI button descriptors from firmware. The fix adds a check for package.count == 0 alongside the existing null pointer check for btns_desc.
Affected products
- <UNKNOWN> Linux kernel from 4.14 onwards (commit 4c3362f44980 and later)
Timeline
- 2026-09-09: disclosed
- 2026-09-25: patched