Asrock
Monthly
ASRock Polychrome SYNC/RGB kernel driver improperly restricts I/O port access via its IOCTL interface, allowing any authenticated local user to force an OS reboot. The driver, installed as part of ASRock's RGB lighting control software for motherboards and VGA cards, accepts crafted IOCTL requests without sufficient validation of target I/O ports, enabling a low-privileged local attacker to cause system-wide availability failure. No public exploit or KEV listing exists at time of analysis; the TWCERT advisory is the primary disclosure source.
Authenticated local attackers on Windows systems running ASRock Polychrome SYNC/RGB can crash the operating system by submitting a specially crafted IOCTL request to the product's installed kernel-mode driver, which dereferences an attacker-supplied pointer without validation (CWE-822). Both the Motherboard (MB) and VGA variants of the software are affected, as confirmed by TWCERT. No public exploit code or active exploitation has been identified; impact is strictly denial of service with no confidentiality or integrity dimension, consistent with the CVSS 4.0 vector scoring VA:H with all other impact metrics at N.
Motherboards from ASRock, ASRockRack, and ASRockInd ship with IOMMU/DMA remapping not properly enabled in firmware, allowing an attacker with physical access to plug in a DMA-capable PCIe device and read or write arbitrary physical memory during the pre-boot window, before the OS kernel and its security features are loaded. Exploitation requires hands-on physical presence at the machine (CVSS 4.0 AV:P, base score 7.0; independent assessment CVSS 3.1 AV:P/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact), so although the technical impact is total memory compromise, the attack does not scale remotely and is limited to the specific board models the vendor lists. No public exploit code has been identified at time of analysis, EPSS is low at 0.35% (26th percentile), and there is no CISA KEV listing indicating confirmed active exploitation, but the affected board list is not fully enumerated in the available advisories and the pre-boot window closes only if a correctly configured OS enables its own IOMMU protection.
AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering a triple fault via a request to zero CR3. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
ASRock Polychrome SYNC/RGB kernel driver improperly restricts I/O port access via its IOCTL interface, allowing any authenticated local user to force an OS reboot. The driver, installed as part of ASRock's RGB lighting control software for motherboards and VGA cards, accepts crafted IOCTL requests without sufficient validation of target I/O ports, enabling a low-privileged local attacker to cause system-wide availability failure. No public exploit or KEV listing exists at time of analysis; the TWCERT advisory is the primary disclosure source.
Authenticated local attackers on Windows systems running ASRock Polychrome SYNC/RGB can crash the operating system by submitting a specially crafted IOCTL request to the product's installed kernel-mode driver, which dereferences an attacker-supplied pointer without validation (CWE-822). Both the Motherboard (MB) and VGA variants of the software are affected, as confirmed by TWCERT. No public exploit code or active exploitation has been identified; impact is strictly denial of service with no confidentiality or integrity dimension, consistent with the CVSS 4.0 vector scoring VA:H with all other impact metrics at N.
Motherboards from ASRock, ASRockRack, and ASRockInd ship with IOMMU/DMA remapping not properly enabled in firmware, allowing an attacker with physical access to plug in a DMA-capable PCIe device and read or write arbitrary physical memory during the pre-boot window, before the OS kernel and its security features are loaded. Exploitation requires hands-on physical presence at the machine (CVSS 4.0 AV:P, base score 7.0; independent assessment CVSS 3.1 AV:P/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact), so although the technical impact is total memory compromise, the attack does not scale remotely and is limited to the specific board models the vendor lists. No public exploit code has been identified at time of analysis, EPSS is low at 0.35% (26th percentile), and there is no CISA KEV listing indicating confirmed active exploitation, but the affected board list is not fully enumerated in the available advisories and the pre-boot window closes only if a correctly configured OS enables its own IOMMU protection.
AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering a triple fault via a request to zero CR3. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.1), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.210, F-Stream before v3.0.210, and RestartToUEFI before v1.0.6.2 expose functionality to. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.