GHSA-XMXV-96VW-VWQC
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
platform/x86: bitland-mifs-wmi: Fix NULL pointer dereference during suspend/resume
The driver registers two distinct WMI devices: a control device (BITLAND_WMI_CONTROL) and an event device (BITLAND_WMI_EVENT). During the probe phase, the event device handling path returns early before initializing the platform profile device (data->pp_dev), leaving it NULL.
However, the PM sleep operations are registered globally for the WMI driver and are triggered for both devices. When entering suspend, the event device invokes bitland_mifs_wmi_suspend(), which passes the uninitialized data->pp_dev (NULL) into laptop_profile_get(). This leads to a NULL pointer dereference inside dev_get_drvdata(), causing a kernel Oops and halting the suspend sequence.
Fix this by adding a validity check for data->pp_dev in both the suspend and resume callbacks, safely skipping profile operations for the event device.
{
"affected": [],
"aliases": [
"CVE-2026-72346"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:07Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: bitland-mifs-wmi: Fix NULL pointer dereference during suspend/resume\n\nThe driver registers two distinct WMI devices: a control device\n(BITLAND_WMI_CONTROL) and an event device (BITLAND_WMI_EVENT). During\nthe probe phase, the event device handling path returns early before\ninitializing the platform profile device (data-\u003epp_dev), leaving it\nNULL.\n\nHowever, the PM sleep operations are registered globally for the WMI\ndriver and are triggered for both devices. When entering suspend, the\nevent device invokes bitland_mifs_wmi_suspend(), which passes the\nuninitialized data-\u003epp_dev (NULL) into laptop_profile_get(). This leads\nto a NULL pointer dereference inside dev_get_drvdata(), causing a\nkernel Oops and halting the suspend sequence.\n\nFix this by adding a validity check for data-\u003epp_dev in both the suspend\nand resume callbacks, safely skipping profile operations for the event\ndevice.",
"id": "GHSA-xmxv-96vw-vwqc",
"modified": "2026-08-15T06:32:21Z",
"published": "2026-08-15T06:32:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72346"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6f2cb20d8e286218d51754f06ee219d8ce754b18"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d3666875c75eb1bc8090343fa0d6fc8fb7924356"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.