Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43332thermal: core: Fix thermal zone device registration error path

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43332, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 335176dd8ebaca6493807dceea33c478305667fa – < 9e796001af97a1f7368d5114b7a8533dd98d797a
    • affected 04e6ccfc93c5a1aa1d75a537cf27e418895e20ea – < 604da9c04c218362e1c1457304ebeb9c199d537c
    • affected 04e6ccfc93c5a1aa1d75a537cf27e418895e20ea – < c4c7219e93319bba9ba0765dee597784c78f63c5
    • affected 04e6ccfc93c5a1aa1d75a537cf27e418895e20ea – < 4d390f0e507dfb16d58f83a58d78d1150dc8b9d7
    • affected 04e6ccfc93c5a1aa1d75a537cf27e418895e20ea – < 9e07e3b81807edd356e1f794cffa00a428eff443
    • affected 02871710b93058eb1249d5847c0b2d1c2c3c98ae
    • affected 6.6.14 – < 6.6.134
    • affected 6.7.2 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43332 badge
[![CVE-2026-43332](https://cveledger.app/badge/CVE-2026-43332.svg)](https://cveledger.app/cve/CVE-2026-43332)

Record last updated .