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-2023-52519HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit

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().

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years 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

CVSS scores of CVE-2023-52519, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2e23a70edabe933284f690dff49497fb6b82b0e5 – < 8781fe259dd5a178fdd1069401bbd1437f9491c5
    • affected 2e23a70edabe933284f690dff49497fb6b82b0e5 – < cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f
    • affected 2e23a70edabe933284f690dff49497fb6b82b0e5 – < 60fb3f054c99608ddb1f2466c07108da6292951e
    • affected 2e23a70edabe933284f690dff49497fb6b82b0e5 – < 8f02139ad9a7e6e5c05712f8c1501eebed8eacfd
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.135 – ≤ 5.15.*
    • unaffected 6.1.57 – ≤ 6.1.*
    • unaffected 6.5.7 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .