CVE-2026-43332: thermal: core: Fix thermal zone device registration error path
In the Linux kernel, the following vulnerability has been resolved:
thermal: core: Fix thermal zone device registration error path
If thermal_zone_device_register_with_trips() fails after registering
a thermal zone device, it needs to wait for the tz->removal completion
like thermal_zone_device_unregister(), in case user space has managed
to take a reference to the thermal zone device's kobject, in which case
thermal_release() may not be called by the error path itself and tz may
be freed prematurely.
Add the missing wait_for_completion() call to the thermal zone device
registration error path.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43332 is a Linux kernel bug in thermal device registration error handling. Under certain failure conditions, the kernel may free thermal-zone data too early while user space still holds a reference. The CVSS score is high, but exploitation requires local access. No provided source indicates active exploitation.
Executive priority
Treat as a high-priority kernel maintenance item, especially for systems with local users or untrusted workloads. It is not currently supported as actively exploited by the provided sources, so prioritize alongside normal emergency kernel patch processes rather than incident response.
Technical view
The Linux thermal core missed a wait_for_completion() call when thermal_zone_device_register_with_trips() fails after registering a thermal zone device. If user space holds a kobject reference, thermal_release() may not run in the error path, creating a premature free condition. Kernel stable commits are referenced as fixes.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or builds containing the vulnerable thermal core code. The source data lists Linux kernels and several stable commit references, but version ranges are unusual and should be validated against distribution advisories.
Exploitation context
The CVSS vector is local, low-complexity, low-privilege, no user interaction, with high confidentiality, integrity, and availability impact. The provided sources do not show KEV listing, public exploitation, or weaponized exploit availability.
Researcher notes
The issue is a lifetime-management bug in the thermal subsystem registration error path. The key fix is adding the missing completion wait to avoid freeing tz before delayed kobject release. Provided affected version data is incomplete or inconsistent, so commit-level and vendor validation are important.
Mitigation direction
Check your Linux distribution or kernel vendor advisory for CVE-2026-43332.
Update to a kernel build that includes the referenced stable fix.
Prioritize shared, multi-user, and untrusted workload hosts.
Reboot systems after kernel update where required.
Track vendor guidance if fixed package availability is unclear.
Validation and detection
Inventory running kernel versions across Linux assets.
Compare builds against vendor advisories and referenced stable commits.
Confirm patched kernels are actually booted after maintenance.
Record exceptions where vendor status is not yet available.
Monitor CISA KEV and vendor updates for exploitation changes.
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-43332 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.