What is CVE-2026-64213?

CVE-2026-64213 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 5.3 onward and patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64213 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64213?

CVE-2026-64213 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-64213?

Yes, CVE-2026-64213 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 5.3 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64213 actively exploited?

CVE-2026-64213 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-64213

Medium

In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm90) Add lock protection to lm90_alert Sashiko reports: lm90_alert() executes in the smbus alert context and calls lm90_update_confreg() to disable the hardware alert line, without acquiring hwmon_lock. Concurrently, sysfs write operations (such as lm90_write_convrate) hold the hwmon_lock, temporarily modify data->config, and then restore it. If an alert interrupt occurs concurrently with a sysfs write, the sysfs path will overwrite the alert handler's modifications to data->config and the hardware register. This unintentionally re-enables the hardware alert line while the alarm is still active, causing an interrupt storm. Add the missing lock to lm90_alert() to solve the problem.

Package Linux Kernel

Published 2026-07-24

Last modified 2026-08-11

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 5.3 and later are affected. Fixed in 6.18.34, 7.0.11, 7.1 and their respective stable series.

Affected from

≥ 5.3

Fixed in

✓ 6.18.34 6.18.x ✓ 7.0.11 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf

Patch
Kernel Git
https://git.kernel.org/stable/c/b0b66aae8a94c3663d47e4000b0e81b89ce32186

Patch
Kernel Git
https://git.kernel.org/stable/c/bed1fc32e0eb653806fa98afcf55f9a311fc4ce2

Patch

Details

CVE ID CVE-2026-64213

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-07-24

Modified 2026-08-11

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64213?

CVE-2026-64213 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 5.3 onward and has been patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64213 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64213?

CVE-2026-64213 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-64213?

Yes. CVE-2026-64213 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 5.3 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64213 actively exploited?

No. CVE-2026-64213 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.