CVE-2009-4419

CVE-2009-4419 is a high-severity vulnerability in Intel Gm45 Chipset with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-16.

Key facts

Description

Intel Q35, GM45, PM45 Express, Q45, and Q43 Express chipsets in the SINIT Authenticated Code Module (ACM), which allows local users to bypass the Trusted Execution Technology protection mechanism and gain privileges by modifying the MCHBAR register to point to an attacker-controlled region, which prevents the SENTER instruction from properly applying VT-d protection while an MLE is being loaded.

Frequently asked questions

What is CVE-2009-4419?
Intel Q35, GM45, PM45 Express, Q45, and Q43 Express chipsets in the SINIT Authenticated Code Module (ACM), which allows local users to bypass the Trusted Execution Technology protection mechanism and gain privileges by modifying the MCHBAR register to point to an attacker-controlled region, which prevents the SENTER instruction from properly applying VT-d protection while an MLE is being loaded.
How severe is CVE-2009-4419?
CVE-2009-4419 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2009-4419 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-4419?
CVE-2009-4419 primarily affects Intel Gm45 Chipset. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2009-4419?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2009-4419 published?
CVE-2009-4419 was published on 2009-12-24 and last updated on 2026-06-16.

References

Affected products (5)

Other CWE-16 vulnerabilities

Browse all CWE-16 vulnerabilities →