Kernel fault via Timer operand stack underflow
Published Sep 18, 2025 · Updated Sep 18, 2025
An array-index error in Linux kernel ACPICA allows local users to trigger an out-of-bounds access via an AML Timer instruction. The Timer opcode accepts no operands but lacks AML_NO_OPERAND_RESOLVE, causing acpi_ds_exec_end_op to resolve a nonexistent operand and index the operand array at -1. Access requires a local path that evaluates ACPI AML, and the published reproduction reports a UBSAN kernel fault through acpi_power_meter.
Summary
What happened
An array-index error in Linux kernel ACPICA allows local users to trigger an out-of-bounds access via an AML Timer instruction. The Timer opcode accepts no operands but lacks AML_NO_OPERAND_RESOLVE, causing acpi_ds_exec_end_op to resolve a nonexistent operand and index the operand array at -1. Access requires a local path that evaluates ACPI AML, and the published reproduction reports a UBSAN kernel fault through acpi_power_meter.
The record
- CVE
- CVE-2023-53395
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <23c67fa615c52712bfa02a6dfadbd4656c87c066
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f2a5905303ae230b5159fcd8cdcd5b3e7ad5e2d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a21ffdbc825e0919db9da0e27ee5ff2cc8a863e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3bf4463e40a17a23f2f261dfd7fe23129bdd04a4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <430787056dd3c591eb553d5c3b2717efcf307d4e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <625c12dc04a607b79f180ef3ee5a12bf2e3324c0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b102113469487b460e9e77fe9e00d49c50fe8c86
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e1f686930ee4b059c7baa3c3904b2401829f2589
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo