Sequence of processor instructions leads to unexpected behavior for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege and/or information disclosure and/or denial of service via local access.
Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Core_i3-10100y_firmware | Intel | - (including) | - (including) |
| Intel-microcode | Ubuntu | bionic | * |
| Intel-microcode | Ubuntu | devel | * |
| Intel-microcode | Ubuntu | esm-infra-legacy/trusty | * |
| Intel-microcode | Ubuntu | esm-infra/bionic | * |
| Intel-microcode | Ubuntu | esm-infra/xenial | * |
| Intel-microcode | Ubuntu | focal | * |
| Intel-microcode | Ubuntu | jammy | * |
| Intel-microcode | Ubuntu | lunar | * |
| Intel-microcode | Ubuntu | mantic | * |
| Intel-microcode | Ubuntu | trusty | * |
| Intel-microcode | Ubuntu | trusty/esm | * |
| Intel-microcode | Ubuntu | xenial | * |
If the instruction set architecture (ISA) and processor logic are not designed carefully and tested thoroughly, certain combinations of instructions may lead to locking the processor or other unexpected and undesirable behavior. Upon encountering unimplemented instruction opcodes or illegal instruction operands, the processor should throw an exception and carry on without negatively impacting security. However, specific combinations of legal and illegal instructions may cause unexpected behavior with security implications such as allowing unprivileged programs to completely lock the CPU.