Linux Kernel up to 7.1.4/7.2-rc2 bitland-mifs-wmi bitland_mifs_wmi_suspend pp_dev null pointer dereference

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.1.4/7.2-rc2. It has been declared as problematic. Affected by this issue is the function bitland_mifs_wmi_suspend of the component bitland-mifs-wmi. The manipulation of the argument pp_dev results in null pointer dereference. This vulnerability is reported as CVE-2026-72346. The attack requires a local approach. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.4/7.2-rc2. It has been classified as problematic. Affected is the function bitland_mifs_wmi_suspend of the component bitland-mifs-wmi. The manipulation of the argument pp_dev with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:

In 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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-72346 since 08/09/2026. The exploitability is told to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

Upgrading to version 7.1.5 or 7.2-rc3 eliminates this vulnerability. Applying the patch 6f2cb20d8e286218d51754f06ee219d8ce754b18/d3666875c75eb1bc8090343fa0d6fc8fb7924356 is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 7.1.0
• 7.1.1
• 7.1.2
• 7.1.3
• 7.1.4
• 7.2-rc1
• 7.2-rc2

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion