Answer in brief
CVE-2026-64603 records a Unknown severity vulnerability in platform/x86: intel-hid: Protect ACPI notify handler against recursion. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <a6402808e552e44e9c26a9fe8395ac11703d5800 || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0 || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <eace3b3e729d5ba11794d69acfafb58a7950217c || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <c085d82613d5618814b84406c8b2d64f1bc305e7 | a6402808e552e44e9c26a9fe8395ac11703d5800, 86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0, eace3b3e729d5ba11794d69acfafb58a7950217c, c085d82613d5618814b84406c8b2d64f1bc305e7 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64603 records a Unknown severity vulnerability in platform/x86: intel-hid: Protect ACPI notify handler against recursion. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <a6402808e552e44e9c26a9fe8395ac11703d5800 || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0 || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <eace3b3e729d5ba11794d69acfafb58a7950217c || >=e2ffcda1629012a2c1a3706432bc45fdc899a584 <c085d82613d5618814b84406c8b2d64f1bc305e7 | a6402808e552e44e9c26a9fe8395ac11703d5800, 86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0, eace3b3e729d5ba11794d69acfafb58a7950217c, c085d82613d5618814b84406c8b2d64f1bc305e7 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.