CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (powerz) Avoid cacheline sharing for DMA buffer
Depending on the architecture the transfer buffer may share a cacheline
with the following mutex. As the buffer may be used for DMA, that is
problematic.
Use the high-level DMA helpers to make sure that cacheline sharing can
not happen.
Also drop the comment, as the helpers are documentation enough.
https://sashiko.dev/#/message/20260408175814.934BFC19421%40smtp.kernel.org
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue fixes unsafe memory layout around a DMA transfer buffer in the powerz hardware-monitoring driver. The source does not provide CVSS, CWE, impact, or exploitability. Treat it as a kernel reliability and hardening update, especially where affected kernels and the powerz driver may be present.
Executive priority
Monitor and patch through normal kernel update channels unless asset inventory shows broad use of the affected driver. Escalation above routine patching is not supported by the current evidence because severity, impact, and exploitation are unspecified.
Technical view
The powerz hwmon driver used a transfer buffer that could share a CPU cacheline with a following mutex. Because the buffer may be used for DMA, cacheline sharing is unsafe on some architectures. The fix switches to higher-level DMA helpers to prevent that layout hazard.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the powerz hwmon driver relevant or enabled. The CVE source lists Linux as affected, but distribution backport status, hardware dependency, and practical attack surface are not established in the provided evidence.
Exploitation context
CISA KEV is false, and the provided sources do not state active exploitation, public exploit availability, or attacker prerequisites. No exploit path is described. The evidence supports a kernel driver memory-safety/DMA correctness issue, not confirmed in-the-wild abuse.
Researcher notes
Key uncertainty is impact. The patch rationale is cacheline sharing with a DMA buffer adjacent to a mutex, fixed through DMA helpers. Validate architecture-specific DMA/cache behavior and driver reachability before assigning urgency beyond routine kernel maintenance.
Mitigation direction
Apply Linux vendor kernel updates containing the referenced stable fixes.
Check distribution advisories for backported fixes and package-specific version mapping.
Prioritize systems using the powerz hwmon driver or related hardware monitoring support.
Follow vendor guidance if no fixed package is available yet.
Validation and detection
Inventory Linux kernel versions across affected server and endpoint fleets.
Check whether the powerz hwmon driver is built, loaded, or packaged.
Confirm installed kernel packages include the referenced stable commits or vendor backports.
Track CVE and distribution advisories for severity or exploitability updates.
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-46007 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:56 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.