Skip to content
Systems

CVE-2026-74604

8.4
High
EPSS 0.14%Patch availableAug 25, 2026

Use-after-free in Linux thermal hwmon may allow kernel crash or local privilege escalation.

common questions

Is CVE-2026-74604 being exploited?

Not confirmed. CVE-2026-74604 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.

How severe is CVE-2026-74604?

CVE-2026-74604 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74604?

Yes. A fix has been recorded for CVE-2026-74604. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74604 affect?

CVE-2026-74604 affects Linux kernel (thermal hwmon subsystem), Kernels containing commit 030a48b0f6ce. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74604?

Apply upstream kernel fix or vendor updates immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (thermal hwmon subsystem)Kernels containing commit 030a48b0f6ce
impact

Local attacker can trigger a use-after-free in thermal_add_hwmon_sysfs to crash the kernel or potentially achieve kernel-level code execution (privilege escalation).

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < 2434f4765da8ccd7ef31be88b86f1bfa2e95be11
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < b4c01ae6dd56d9dfd96bd1b29c28afa8fa06b366
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < 999e573212d5f1debf073c68be35e55bbfad12fc
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < 6a48ee9a5bda0f8ee501f9bef159fb9f39ff519a
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < 8d34019d1413629a434a7e8d9f91c76d256196a0
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < 6b446d335ba16e93a266dd77adf1ba51abc82df4
  • affected>= 030a48b0f6ce393d78b8d33debb1e2043b8cc156 and < ff8da20b6f47c48d46e47f93f7a59e2d56ee9107
  • affected5.11
vendor says fixed in< 5.11, >= 5.15.216 and <= 5.15.*, >= 6.1.183 and <= 6.1.*, >= 6.6.152 and <= 6.6.*, >= 6.12.104 and <= 6.12.*, >= 6.18.45 and <= 6.18.*, >= 7.1.9 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free