CVE-2026-43332

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

thermal: core: Fix thermal zone device registration error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4c7219e93319bba9ba0765dee597784c78f63c5
generic

thermal: core: Fix thermal zone device registration error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e796001af97a1f7368d5114b7a8533dd98d797a
generic

thermal: core: Fix thermal zone device registration error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e07e3b81807edd356e1f794cffa00a428eff443
generic

thermal: core: Fix thermal zone device registration error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/604da9c04c218362e1c1457304ebeb9c199d537c
generic

thermal: core: Fix thermal zone device registration error path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d390f0e507dfb16d58f83a58d78d1150dc8b9d7

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.134—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 215 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 19:15 UTCEG score recompute
  20. 2026-08-23 19:15 UTCVendor advisory
  21. 2026-08-23 19:15 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 11:56 UTCEG score recompute
  4. 2026-08-17 11:56 UTCVendor advisory
  5. 2026-08-17 11:56 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 04:37 UTCEG score recompute
  8. 2026-08-16 04:37 UTCVendor advisory
  9. 2026-08-16 04:37 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 15:41 UTCVendor advisory
  13. 2026-08-14 15:41 UTCGHSA enrichment
  14. 2026-08-14 03:11 UTCEG score recompute
  15. 2026-08-14 03:11 UTCVendor advisory
  16. 2026-08-14 03:11 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 05:59 UTCVendor advisory
  19. 2026-08-13 05:59 UTCGHSA enrichment
  20. 2026-08-12 16:49 UTCEG score recompute
  21. 2026-08-12 16:49 UTCVendor advisory
  22. 2026-08-12 16:49 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 15:52 UTCEG score recompute
  25. 2026-08-11 15:52 UTCVendor advisory
  26. 2026-08-11 15:52 UTCGHSA enrichment
  27. 2026-08-11 13:43 UTCEPSS rescore
  28. 2026-08-11 01:19 UTCEG score recompute
  29. 2026-08-11 01:19 UTCVendor advisory
  30. 2026-08-11 01:19 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 03:26 UTCVendor advisory
  33. 2026-08-10 03:25 UTCGHSA enrichment
  34. 2026-08-09 14:56 UTCVendor advisory
  35. 2026-08-09 14:56 UTCGHSA enrichment
  36. 2026-08-09 02:26 UTCEG score recompute
  37. 2026-08-09 02:26 UTCVendor advisory
  38. 2026-08-09 02:26 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 09:49 UTCVendor advisory
  41. 2026-08-08 09:49 UTCGHSA enrichment
  42. 2026-08-07 21:19 UTCEG score recompute
  43. 2026-08-07 21:19 UTCVendor advisory
  44. 2026-08-07 21:19 UTCGHSA enrichment
  45. 2026-08-07 08:49 UTCVendor advisory
  46. 2026-08-07 08:49 UTCGHSA enrichment
  47. 2026-08-06 16:52 UTCEG score recompute
  48. 2026-08-06 16:52 UTCVendor advisory
  49. 2026-08-06 16:52 UTCGHSA enrichment
  50. 2026-08-06 13:46 UTCEPSS rescore
  51. 2026-08-06 02:20 UTCEG score recompute
  52. 2026-08-06 02:20 UTCVendor advisory
  53. 2026-08-06 02:20 UTCGHSA enrichment
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-05 13:50 UTCEG score recompute
  56. 2026-08-05 13:50 UTCVendor advisory
  57. 2026-08-05 13:50 UTCGHSA enrichment
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:38 UTCEPSS rescore
  60. 2026-08-03 19:33 UTCEG score recompute
  61. 2026-08-03 19:33 UTCVendor advisory
  62. 2026-08-03 19:33 UTCGHSA enrichment
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 04:26 UTCVendor advisory
  65. 2026-08-03 04:26 UTCGHSA enrichment
  66. 2026-08-02 15:37 UTCVendor advisory
  67. 2026-08-02 15:37 UTCGHSA enrichment
  68. 2026-08-02 03:07 UTCEG score recompute
  69. 2026-08-02 03:07 UTCVendor advisory
  70. 2026-08-02 03:07 UTCGHSA enrichment
  71. 2026-08-02 02:27 UTCEPSS rescore
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-28 15:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43332?
CVE-2026-43332 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: thermal: core: Fix thermal zone device registration error path If thermalzonedeviceregisterwith_trips() fails after registering a thermal zone device, it needs to wait for the tz->removal completion like…
When was CVE-2026-43332 disclosed?
CVE-2026-43332 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43332 actively exploited?
CVE-2026-43332 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43332?
CVE-2026-43332 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43332?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43332, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43332

Explore →

Is Your Infrastructure Affected by CVE-2026-43332?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs