What is CVE-2026-64238?

CVE-2026-64238 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Improper Locking flaw (CWE-667), affecting Linux kernel versions from 6.19.12 onward and patched in 7.0.12 and 7.1. CVE-2026-64238 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

CVE-2026-64238 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-64238?

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

Is CVE-2026-64238 actively exploited?

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

What is Improper Locking (CWE-667)?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/667.html

CVE-2026-64238

Medium

In the Linux kernel, the following vulnerability has been resolved: gpio: shared: fix deadlock on shared proxy's parent removal Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent. Make the critical section shorter - only protect the offset when it's being read. While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

Package Linux Kernel

Published 2026-07-24

Last modified 2026-08-13

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

Weakness type

CWE-667

CVE-2026-64238 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.19.12, 7.0 and later are affected. Fixed in 7.0.12, 7.1 and their respective stable series.

Affected from

≥ 6.19.12 ≥ 7.0

Fixed in

✓ 7.0.12 7.0.x ✓ 7.1

References

2 total

Kernel Git
https://git.kernel.org/stable/c/a1b836607304f71051f9f9dcccf8b5097b86a1fb

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

Patch

Details

CVE ID CVE-2026-64238

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-07-24

Modified 2026-08-13

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64238?

CVE-2026-64238 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 6.19.12 onward and has been patched in 7.0.12 and 7.1. CVE-2026-64238 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64238?

CVE-2026-64238 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-64238?

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

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