CVE-2026-99717: hwmon: (pmbus/q54sj108a2) Add missing NULL pointer check
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/q54sj108a2) Add missing NULL pointer check
When CONFIGDEBUGFS is enabled and per-client PMBus debugfs directory creation fails during pmbusdoprobe(), q54sj108a2probe() passes the NULL pointer returned by pmbusgetdebugfsdir() to debugfscreatedir() without validation, creating its debugfs directory at the debugfs root instead of under the client directory.
If pmbusinitdebugfs() fails to create the client directory, data->debugfs is left as NULL or an ERRPTR, which pmbusgetdebugfsdir() converts to NULL. Passing a NULL parent to debugfscreatedir() places q54sj108a2dir in the root of the debugfs filesystem and populates it with attribute files whose private data pointers reference psu->debugfsentries. Because this root-level directory is outside the client debugfs hierarchy, PMBus core cleanup does not remove it on device unbind, leaking the debugfs entries and causing a use-after-free of the devm-allocated struct q54sj108a2data if the orphaned files are accessed via q54sj108a2debugfsread() or q54sj108a2debugfswrite() after device removal.
Fix the problem by adding the missing NULL pointer check.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Compensating control
In q54sj108a2_probe(), add a NULL-pointer check for the directory returned by pmbus_get_debugfs_dir() before passing it to debugfs_create_dir().
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel q54sj108a2 PMBus hardware-monitor driver are exposed only when CONFIG_DEBUG_FS is enabled and creation of the per-client PMBus debugfs directory fails during device probing.
What must happen for the use-after-free to be triggered?
The failed debugfs-directory creation must cause the driver to create an orphaned directory at the debugfs root. After the associated device is unbound and its devm-allocated driver data is freed, an attacker or local user would need to access the orphaned debugfs files through the driver's debugfs read or write handlers.
How can I tell whether a device may already be affected?
Look for a q54sj108a2_dir directory at the root of the debugfs filesystem rather than within the relevant PMBus client debugfs hierarchy. Its presence after the associated device has been removed indicates orphaned debugfs entries may remain.
Is the default configuration affected?
The vulnerable path requires CONFIG_DEBUG_FS to be enabled. The provided information does not establish whether that option is enabled by default in a particular kernel distribution or deployment.