Technical impact
A flaw in Chrome’s Device Trust mechanism on Windows fails to validate untrusted input properly, allowing a remote attacker who has already compromised the renderer process to supply a crafted input that could potentially trigger the device trust flaw and escape the browser sandbox. The input validation weakness is classified as CWE‑20.
Affected Systems
Google Chrome for Windows versions earlier than 150.0.7871.47 are affected. All stable channel releases prior to that point contain the vulnerability; upgrades to 150.0.7871.47 or later contain the fix.
Risk and Exploitability
The EPSS score remains < 1% and the vulnerability is not listed in KEV, but the CVSS score of 9.6 indicates a critical risk. The likely attack vector is a crafted HTML page served to a user after the attacker has compromised the renderer process. Once the renderer process is compromised, the attacker could then trigger the device trust flaw to escape the sandbox and execute arbitrary code, making the potential impact severe.
Debian DLA
Debian DSA