CVE-2026-64603

In the Linux kernel, the following vulnerability has been resolved: platform/x86: intel-hid: Protect ACPI notify handler against recursion Since commit e2ffcda16290 ("ACPI: OSL: Allow Notify () handlers to run on all CPUs") ACPI notify handlers like the intel-hid notify_handler() may run on multiple CPU cores racing with themselves. On convertibles and detachables (matched by DMI chassis-type 31 and 32 in dmi_auto_add_switch[]) the SW_TABLET_MODE input device is registered lazily from notify_handler() on the first tablet-mode event, via intel_hid_switches_setup(). When two such events race on different CPUs both can pass the !priv->switches check and register the priv->switches input device twice, resulting in a duplicate sysfs entry and a subsequent NULL pointer dereference. This is the same class of bug fixed by commit e075c3b13a0a ("platform/x86: intel-vbtn: Protect ACPI notify handler against recursion") for the sibling intel-vbtn driver. Protect intel-hid notify_handler() from racing with itself with a mutex to fix this.

Package Linux Kernel
Published 2026-08-06
Last modified 2026-08-06
Patch available
Yes

Affected versions

Linux kernel versions 6.8 and later are affected. Fixed in 6.12.96, 6.18.39, 7.1.4, 7.2-rc1 and their respective stable series.

Affected from
≥ 6.8
Fixed in
✓ 6.12.96 6.12.x ✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2-rc1

Frequently asked questions

  • What is CVE-2026-64603?

    CVE-2026-64603 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.8 onward and has been patched in 6.12.96, 6.18.39, 7.1.4 and others. CVE-2026-64603 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64603?

    Yes. CVE-2026-64603 has been patched. Fixed versions include 6.12.96, 6.18.39, 7.1.4 and others. If you are running Linux kernel 6.8 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64603 actively exploited?

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