CVE-2025-20109

High
7.8
0.05.010.0
Year
2025
Published
Aug 12, 2025
Known Affected Devices
0
CVSS Score
7.8

What is CVE-2025-20109?

Improper Isolation or Compartmentalization in the stream cache mechanism for some Intel(R) Processors may allow an authenticated user to potentially enable escalation of privilege via local access.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
AV
Attack Vector
Local

Requires local access — attacker must be logged in or have physical access to the device.

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
Low

Basic user account required (e.g. standard login without admin rights).

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Changed

Exploiting the vulnerability can affect other components beyond the vulnerable one.

C
Confidentiality Impact
High

Complete loss of confidentiality. All data on the component may be exposed.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
High

Complete denial of service. The component becomes fully unavailable.

Known Affected Devices

FAQ

How severe is CVE-2025-20109?

CVE-2025-20109 has a CVSS score of 7.8/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.

What does the CVSS score mean for CVE-2025-20109?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2025-20109 scores 7.8/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2025-20109?

The list of devices confirmed to be affected by CVE-2025-20109 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2025-20109?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.