Paul Grosen

**Name of the Vulnerable Software and Affected Versions** Intel(R) Processors (affected versions not specified) **Description** The issue is related to improper Finite State Machines (FSMs) in the hardware logic of some Intel(R) Processors. This may allow a privileged user to potentially enable denial of service via local access. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Intel(R) Processors (affected versions not specified) **Description** A protection mechanism failure in the SPP for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Intel(R) Xeon(R) processor family (E-Core) (affected versions not specified) **Description** A protection mechanism failure in the SPP for some Intel(R) Xeon(R) processor family (E-Core) may allow an authenticated user to potentially enable escalation of privilege via local access. This issue could let an authenticated user increase their privileges through local access. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Intel(R) Processors (affected versions not specified) Description: The issue is related to improper isolation in the stream cache mechanism of some Intel(R) Processors, which may allow an authenticated user to potentially enable escalation of privilege via local access. This could be exploited by an attacker to gain elevated privileges. The vulnerability is associated with the incorrect isolation of shared resources between trusted and untrusted agents in the processor's microcode. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Intel(R) Core(TM) Ultra Processor (affected versions not specified) **Description** The issue is related to improper isolation in the stream cache mechanism, which may allow an authenticated user to potentially enable escalation of privilege via local access. This is due to the incorrect isolation of shared resources between trusted and untrusted agents. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Intel Processors (affected versions not specified) **Description** A sequence of processor instructions can lead to unexpected behavior in some Intel processors, potentially allowing an authenticated user to enable escalation of privilege, information disclosure, or denial of service via local access. This issue is related to the interpretation of redundant prefixes and can cause the system to crash or become unresponsive. The vulnerability, termed Reptar, primarily affects multi-tenant virtualized environments where multiple virtual machines are run on the same host. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Medtronic MyCareLink Smart 25000 all versions **Description** The issue allows an attacker who gains authentication to run a debug command, which is sent to the reader, causing a heap overflow in the MCL Smart Reader stack. This heap overflow enables the attacker to remotely execute code on the MCL Smart Reader, potentially leading to control of the device. **Recommendations** For Medtronic MyCareLink Smart 25000 all versions, as a temporary workaround, consider restricting access to the debug command until a patch is available. Additionally, restrict access to the MCL Smart Reader to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.