CVE-2023-52519

HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit

HIGH
7.1
CVSS Score
Published: March 2, 2024 at 09:52 PM UTC
Updated: June 17, 2026 at 06:42 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit The EHL (Elkhart Lake) based platforms provide a OOB (Out of band) service, which allows to wakup device when the system is in S5 (Soft-Off state). This OOB service can be enabled/disabled from BIOS settings. When enabled, the ISH device gets PME wake capability. To enable PME wakeup, driver also needs to enable ACPI GPE bit. On resume, BIOS will clear the wakeup bit. So driver need to re-enable it in resume function to keep the next wakeup capability. But this BIOS clearing of wakeup bit doesn't decrement internal OS GPE reference count, so this reenabling on every resume will cause reference count to overflow. So first disable and reenable ACPI GPE bit using acpi_disable_gpe().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.12 ≤ v < 5.15.1355.12 ≤ v < 6.1.575.12 ≤ v < 6.5.75.12 ≤ v < 6.65.16 ≤ v < 6.1.576.2 ≤ v < 6.5.72e23a70edabe933284f690dff49497fb6b82b0e56.6 rc16.6 rc26.6 rc36.6 rc4
Vendor states this is fixed in 60fb3f054c99608ddb1f2466c07108da6292951e (fixed)
Vendor states this is fixed in 8781fe259dd5a178fdd1069401bbd1437f9491c5 (fixed)
Vendor states this is fixed in 8f02139ad9a7e6e5c05712f8c1501eebed8eacfd (fixed)
Vendor states this is fixed in cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f (fixed)
Vendor states this is fixed in 5.12 (unaffected)
Vendor states this is fixed in 5.15.135 (unaffected)
Vendor states this is fixed in 6.1.57 (unaffected)
Vendor states this is fixed in 6.5.7 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/60fb3f054c99608ddb1f2466c07108da6292951e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8781fe259dd5a178fdd1069401bbd1437f9491c5
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8f02139ad9a7e6e5c05712f8c1501eebed8eacfd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card