CVE-2026-98397
Last modified
CVE-2026-98397 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: platform/x86: x86-android-tablets: hold device reference for secondary fwnode teardown In gpio_secondary_fwnode_init(), acpi_bus_find_device_by_name() returns a device reference, but the local dev variable is declared with __free(put_device), dropping the reference at the end of each iteration. Meanwhile, devm_add_action_or_reset() saves the dev pointer for gpio_secondary_unset() without incrementing its reference count, which could lead to a use-after-free during driver teardown if the device is released in the interim. Acquire an explicit device reference with get_device() when registering the devres action, and drop it with put_device() inside gpio_secondary_unset()..
Description
In the Linux kernel, the following vulnerability has been resolved: platform/x86: x86-android-tablets: hold device reference for secondary fwnode teardown In gpio_secondary_fwnode_init(), acpi_bus_find_device_by_name() returns a device reference, but the local dev variable is declared with __free(put_device), dropping the reference at the end of each iteration. Meanwhile, devm_add_action_or_reset() saves the dev pointer for gpio_secondary_unset() without incrementing its reference count, which could lead to a use-after-free during driver teardown if the device is released in the interim. Acquire an explicit device reference with get_device() when registering the devres action, and drop it with put_device() inside gpio_secondary_unset().
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1448c2d2ca5cc7f4ea6694e6bc809946de0a751c, < c62b6e081119f2ab03cfcafde1f83c0f50e8e726; >= 1448c2d2ca5cc7f4ea6694e6bc809946de0a751c, < 144113b0a70fa18033a747ee5db6803308f7688c |
| Linux | Linux | 7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98397?
How severe is CVE-2026-98397?
How do I fix CVE-2026-98397?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98391In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98392In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98393In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98394In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98395In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98396In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98398In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98399In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98400In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98401In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98402In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98403In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98397?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
