Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64603platform/x86: intel-hid: Protect ACPI notify handler against recursion

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 11 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e2ffcda1629012a2c1a3706432bc45fdc899a584 – < a6402808e552e44e9c26a9fe8395ac11703d5800
    • affected e2ffcda1629012a2c1a3706432bc45fdc899a584 – < 86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0
    • affected e2ffcda1629012a2c1a3706432bc45fdc899a584 – < eace3b3e729d5ba11794d69acfafb58a7950217c
    • affected e2ffcda1629012a2c1a3706432bc45fdc899a584 – < c085d82613d5618814b84406c8b2d64f1bc305e7
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64603 badge
[![CVE-2026-64603](https://cveledger.app/badge/CVE-2026-64603.svg)](https://cveledger.app/cve/CVE-2026-64603)

Record last updated .