VulnerabilityPublished 12 Jul 2024Updated 30 Oct 2026

CVE-2024-40975: Linux kernel · platform/x86: x86-android-tablets: Unregister devices in reverse order

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:33 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

AI-suggested

A fix has been implemented in the Linux kernel to unregister devices in reverse order in the x86-android-tablets platform, preventing the described warnings and potential issues. Users should update to the fixed kernel version once available. No additional mitigation steps are specified.

Description

CVE-2024-40975 addresses a Linux kernel vulnerability in the x86-android-tablets platform where devices were not unregistered in reverse order, potentially causing warnings or issues when device consumers still hold references during device removal. The flaw could trigger warnings in the regulator subsystem if a regulator device is unregistered while still referenced by consumers. The fix ensures devices are unregistered in reverse order to prevent such issues.

Impact

If unregistered devices still have active consumers holding references, kernel warnings (WARN()) can occur, indicating improper device removal sequencing. This can lead to instability or unexpected behavior in device management, particularly affecting power regulator devices on certain Android tablet models. However, no direct exploitation or security breach is indicated.

Summary

This vulnerability in the Linux kernel's x86-android-tablets platform involves improper device unregistration order. Specifically, devices were unregistered in an order that could cause consumers of a device to still hold references when the device was removed, leading to kernel warnings such as those in the regulator subsystem. For example, on certain Lenovo Yoga Tablet models, the bq24190 charger chip's regulator device and its consumers (like the lc824206xa micro-USB switch) must be unregistered in reverse order to avoid dummy regulator references and WARN() calls. The patch changes x86_android_tablet_remove() to unregister all device types in reverse order to maintain proper device dependency handling and avoid such warnings.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 15:33 UTC

Technical details

References

Community reviews

Related threats