CVE-2023-52519: HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 60fb3f054c99608ddb1f2466c07108da6292951e, 8781fe259dd5a178fdd1069401bbd1437f9491c5, 8f02139ad9a7e6e5c05712f8c1501eebed8eacfd.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 60fb3f054c99608ddb1f2466c07108da6292951e, 8781fe259dd5a178fdd1069401bbd1437f9491c5, 8f02139ad9a7e6e5c05712f8c1501eebed8eacfd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Mar 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.12affected
- 2e23a70edabe933284f690dff49497fb6b82b0e5 and later · before 8781fe259dd5a178fdd1069401bbd1437f9491c5affected · git
- 2e23a70edabe933284f690dff49497fb6b82b0e5 and later · before cdcc04e844a2d22d9d25cef1e8e504a174ea9f8faffected · git
- 2e23a70edabe933284f690dff49497fb6b82b0e5 and later · before 60fb3f054c99608ddb1f2466c07108da6292951eaffected · git
- 2e23a70edabe933284f690dff49497fb6b82b0e5 and later · before 8f02139ad9a7e6e5c05712f8c1501eebed8eacfdaffected · git
- before 5.12not affected · semver
- 5.15.135 and later · up to and including 5.15.*not affected · semver
- 6.1.57 and later · up to and including 6.1.*not affected · semver
- 6.5.7 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.12 and later · before 5.15.135
- linux linux kernel5.16 and later · before 6.1.57
- linux linux kernel6.2 and later · before 6.5.7
- linux linux kernel6.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.5.8-1 | 6.5.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52517Mar 2, 2024 · spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain28Monitor
- ← EarlierCVE-2023-52518Mar 2, 2024 · Bluetooth: hci_codec: Fix leaking content of local_codecs22Monitor
- Later →CVE-2023-52520Mar 2, 2024 · platform/x86: think-lmi: Fix reference leak22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 60fb3f054c99608ddb1f2466c07108da6292951e | Vendor (CNA) |
| Linux Linux | 8781fe259dd5a178fdd1069401bbd1437f9491c5 | Vendor (CNA) |
| Linux Linux | 8f02139ad9a7e6e5c05712f8c1501eebed8eacfd | Vendor (CNA) |
| Linux Linux | cdcc04e844a2d22d9d25cef1e8e504a174ea9f8f | Vendor (CNA) |
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0160 · Mar 4, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.