CVE-2026-64603
CVE CVE-2026-64603EUVD EUVD-2026-53789Published 2026-08-06T07:13:55.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.96; e2ffcda1629012a2c1a3706432bc45fdc899a584 <a6402808e552e44e9c26a9fe8395ac11703d5800; patch: 0; patch: 6.18.39; e2ffcda1629012a2c1a3706432bc45fdc899a584 <86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0; 6.8; patch: 7.1.4; e2ffcda1629012a2c1a3706432bc45fdc899a584 <eace3b3e729d5ba11794d69acfafb58a7950217c; e2ffcda1629012a2c1a3706432bc45fdc899a584 <c085d82613d5618814b84406c8b2d64f1bc305e7; patch: 7.2-rc1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.