Skip to content
Heist/ feed
UnratedFix available

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

Type: advisorySource: OSV1 source record

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.

Announced Source revision 1
Original source ↗

CVE-2026-64603

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: osv:CVE-2026-64603

Kernel

Source reference: /affected/1/package/name

Affected versions
Not stated in this record
Fixed versions
6.12.96

Source reference: /affected/1/ranges

6.18.39

Source reference: /affected/1/ranges

7.1.4

Source reference: /affected/1/ranges

Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "ranges": [
      {
        "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
        "type": "GIT",
        "events": [
          {
            "introduced": "e2ffcda1629012a2c1a3706432bc45fdc899a584"
          },
          {
            "fixed": "a6402808e552e44e9c26a9fe8395ac11703d5800"
          },
          {
            "fixed": "86df6499dfd232fbc1c82c0d6eb9322ca67b8cd0"
          },
          {
            "fixed": "eace3b3e729d5ba11794d69acfafb58a7950217c"
          },
          {
            "fixed": "c085d82613d5618814b84406c8b2d64f1bc305e7"
          }
        ]
      }
    ],
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64603.json"
    }
  },
  {
    "ranges": [
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.8.0"
          },
          {
            "fixed": "6.12.96"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.13.0"
          },
          {
            "fixed": "6.18.39"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.19.0"
          },
          {
            "fixed": "7.1.4"
          }
        ]
      }
    ],
    "package": {
      "name": "Kernel",
      "ecosystem": "Linux"
    },
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64603.json"
    }
  }
]
Related CVEs
CVE-2026-64603

Source reference: /id

Publisher severity

No explicit severity was provided.

Event
#50749 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement