AMD Radeon RGB tool - signature verification on files in the installation directory: The Radeon RGB tool does

Impact

The Radeon RGB tool does not verify signatures on files placed in its installation directory, so a planted file runs with elevated privileges. A cosmetic utility that escalates to code execution - the reason it appears here is that vendor GPU tooling gets installed wholesale on GPU hosts without anyone asking what the LED control daemon is doing running as root.

Who can reach it

Local, requires write access to the tool's installation directory.

What to do

Update or, better, uninstall - RGB lighting control has no business on a datacenter GPU node. Removing unnecessary vendor tooling from the golden image is the durable fix and costs nothing at runtime. No reboot needed to uninstall.

References

Related entries

• Intel Neural Compressor (SQL injection, second instance): A second SQL-injection path in Neural Compressor reachableCVE-2024-39766 · Intel Neural Compressor (SQL injection, second instance)High
• Redis: Authenticated user triggers a stack/heap out-of-bounds write in hyperloglog opsCVE-2025-32023 · RedisHigh
• Sidero Omni: SAML assertion replay race lets a captured saml-session token be redeemed more than onceCVE-2026-45720 · Sidero Omni (SAML session interceptor, internal/pkg/auth/interceptor/saml.go)High
• Redis (multi-bulk command protocol handling): PERMANENT, VENDOR-ACKNOWLEDGED DENIAL OF SERVICE WITH NO FIX PLANNED. AnNCVD-2025-021-redis-multi-bulk-command-protoco · Redis (multi-bulk command protocol handling)High
• AMD AGESA bootloader - DDR5 PMIC default configuration: The AGESA bootloader leaves DDR5 memory modules in an insecureCVE-2025-48516 · AMD AGESA bootloader - DDR5 PMIC default configurationMedium
• AMD Graphics Driver - out-of-bounds write: Improper input validation lets a local attacker write out of bounds throughCVE-2025-48518 · AMD Graphics Driver - out-of-bounds writeMedium