ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 23c67fa615c52712bfa02a6dfadbd4656c87c066, Kernel 2f2a5905303ae230b5159fcd8cdcd5b3e7ad5e2d, Kernel 3a21ffdbc825e0919db9da0e27ee5ff2cc8a863e and 5 more.
In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruction. For taking care of no argument, AML_NO_OPERAND_RESOLVE flag is added to ASL Timer instruction opcode. When ASL timer instruction interpreted by ACPI interpreter, getting error. After adding AML_NO_OPERAND_RESOLVE flag to ASL Timer instruction opcode, issue is not observed. ============================================================= UBSAN: array-index-out-of-bounds in acpica/dswexec.c:401:12 index -1 is out of range for type 'union acpi_operand_object *[9]' CPU: 37 PID: 1678 Comm: cat Not tainted 6.0.0-dev-th500-6.0.y-1+bcf8c46459e407-generic-64k HW name: NVIDIA BIOS v1.1.1-d7acbfc-dirty 12/19/2022 Call trace: dump_backtrace+0xe0/0x130 show_stack+0x20/0x60 dump_stack_lvl+0x68/0x84 dump_stack+0x18/0x34 ubsan_epilogue+0x10/0x50 __ubsan_handle_out_of_bounds+0x80/0x90 acpi_ds_exec_end_op+0x1bc/0x6d8 acpi_ps_parse_loop+0x57c/0x618 acpi_ps_parse_aml+0x1e0/0x4b4 acpi_ps_execute_method+0x24c/0x2b8 acpi_ns_evaluate+0x3a8/0x4bc acpi_evaluate_object+0x15c/0x37c acpi_evaluate_integer+0x54/0x15c show_power+0x8c/0x12c [acpi_power_meter]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.12, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <23c67fa615c52712bfa02a6dfadbd4656c87c066, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2f2a5905303ae230b5159fcd8cdcd5b3e7ad5e2d, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3a21ffdbc825e0919db9da0e27ee5ff2cc8a863e, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3bf4463e40a17a23f2f261dfd7fe23129bdd04a4, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <430787056dd3c591eb553d5c3b2717efcf307d4e, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <625c12dc04a607b79f180ef3ee5a12bf2e3324c0, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b102113469487b460e9e77fe9e00d49c50fe8c86, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e1f686930ee4b059c7baa3c3904b2401829f2589 | 23c67fa615c52712bfa02a6dfadbd4656c87c066, 2f2a5905303ae230b5159fcd8cdcd5b3e7ad5e2d, 3a21ffdbc825e0919db9da0e27ee5ff2cc8a863e, 3bf4463e40a17a23f2f261dfd7fe23129bdd04a4, 430787056dd3c591eb553d5c3b2717efcf307d4e, 625c12dc04a607b79f180ef3ee5a12bf2e3324c0, b102113469487b460e9e77fe9e00d49c50fe8c86, e1f686930ee4b059c7baa3c3904b2401829f2589 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket