CVE-2026-31486: hwmon: (pmbus/core) Protect regulator operations with mutex
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/core) Protect regulator operations with mutex
The regulator operations pmbus_regulator_get_voltage(),
pmbus_regulator_set_voltage(), and pmbus_regulator_list_voltage()
access PMBus registers and shared data but were not protected by
the update_lock mutex. This could lead to race conditions.
However, adding mutex protection directly to these functions causes
a deadlock because pmbus_regulator_notify() (which calls
regulator_notifier_call_chain()) is often called with the mutex
already held (e.g., from pmbus_fault_handler()). If a regulator
callback then calls one of the now-protected voltage functions,
it will attempt to acquire the same mutex.
Rework pmbus_regulator_notify() to utilize a worker function to
send notifications outside of the mutex protection. Events are
stored as atomics in a per-page bitmask and processed by the worker.
Initialize the worker and its associated data during regulator
registration, and ensure it is cancelled on device removal using
devm_add_action_or_reset().
While at it, remove the unnecessary include of linux/of.h.
Security readout for executives and security teams
Plain-English summary
A Linux PMBus driver race can corrupt voltage-control behavior or crash affected systems when concurrent regulator operations access shared state. Exploitation requires local, low-privileged access according to the supplied CVSS vector. Confidentiality impact is not indicated, but integrity and availability impacts may be high.
Executive priority
Treat as a high-priority targeted kernel update, especially for shared systems or PMBus-managed appliances. It is not supported as an internet-wide emergency because access is local and active exploitation is unconfirmed. Use normal emergency-change processes where voltage integrity or uptime is safety-critical.
Technical view
PMBus voltage get, set, and list operations accessed registers and shared data without update_lock protection. The fix serializes those operations and moves regulator notifications to a worker, avoiding recursive mutex acquisition and deadlock. Events are retained in per-page atomic bitmasks until processed.
Likely exposure
Exposure is most likely on affected Linux systems using PMBus hardware-monitoring regulator functionality. The supplied affected-version data is ambiguous and includes commit identifiers, so determine exposure using distribution advisories, kernel provenance, configuration, and inclusion of the referenced fixes.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. It indicates high integrity and availability impact without confidentiality impact. The bundle says KEV is false and provides no evidence of active exploitation or a public exploit.
Researcher notes
The security issue is the original unsynchronized access, while straightforward locking introduced a notifier re-entry deadlock. The resolution combines mutex protection with deferred notification processing. Exact vulnerable and fixed release boundaries cannot be reliably reconstructed from the supplied version list; assess individual stable-tree or distribution backports.
Mitigation direction
Apply a vendor-supported kernel containing the applicable referenced stable fix.
Check Linux distribution advisories for corrected package versions and required reboot instructions.
Prioritize exposed multi-user or appliance systems that actively use PMBus regulator functionality.
Avoid inventing version thresholds; confirm backports through vendor package changelogs or source provenance.
Validation and detection
Inventory running kernel versions, distributions, and package build identifiers.
Determine whether PMBus regulator drivers and relevant hardware are present and active.
Confirm the installed kernel source includes the applicable referenced stable commit.
After updating, verify the corrected kernel is running following any required reboot.
Regression-test concurrent voltage operations and regulator notifications in a safe hardware test environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31486 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.