VulnerabilityPublished 14 Oct 2026Updated 28 Oct 2026

CVE-2026-98397: Linux kernel · platform/x86: x86-android-tablets: hold device reference for secondary fwnode teardown

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-98397· Medium

Not known to be exploited.

Data as of 28 Oct 2026, 22:28 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSlinux-aws-6.14`pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1007.7~24.04.1 – 6.14.0-1018.18~24.04.1 11 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-aws-6.17`pkg:deb/ubuntu/linux-aws-6.17?arch=source&distro=noble`Other threats	Affected 6.17.0-1005.5~24.04.2 – 6.17.0-1020.20~24.04.1 10 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.11`pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=noble`Other threats	Affected 6.11.0-1008.8~24.04.1 – 6.11.0-1018.18~24.04.1 7 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.14`pkg:deb/ubuntu/linux-azure-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1010.10~24.04.1 – 6.14.0-1017.17~24.04.1 5 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-6.17`pkg:deb/ubuntu/linux-azure-6.17?arch=source&distro=noble`Other threats	Affected 6.17.0-1008.8~24.04.1 – 6.17.0-1022.22 10 affected builds	Fixed in–
Ubuntu 24.04 LTSlinux-azure-fde-6.14`pkg:deb/ubuntu/linux-azure-fde-6.14?arch=source&distro=noble`Other threats	Affected 6.14.0-1012.12~24.04.1 – 6.14.0-1017.17~24.04.1 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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().

References

Community reviews

Loading reviews…