Skip to content
Noroxi
CVE-2025-54514· NVD / CVE Program· CNA AMD

Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a

Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

MediumCVSS 4.8 · v4.0—No exploit No fix recorded
Published
Feb 10, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 1th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

19

Monitor

Low priority for now.

CVSS
19 / 40 · 4.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · AMD
4.8
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.

  • AMD AMD EPYC™ 9005 Series Processors

    • TurinPI 1.0.0.6not affected

  • AMD AMD EPYC™ Embedded 9005 Series Processors

    • EmbTurinPI-SP5_1.0.0.1not affected

  • AMD AMD Ryzen™ 9000 Series Desktop Processors

    • ComboAM5 PI 1.2.0.3hnot affected

  • AMD AMD Ryzen™ 9000HX Series Processors

    • FireRangeFL1 PI-1.0.0.0dnot affected

  • AMD AMD Ryzen™ AI 300 Series Processors

    • StrixKrackanPI-FP8_1.1.0.0d, GorgonPI-FP8_1.0.0.0not affected

  • AMD AMD Ryzen™ AI 400 Series Processors

    • GorgonPI-FP8_1.0.0.0not affected

  • AMD AMD Ryzen™ AI Max 300 Series Processors

    • StrixHaloPI-FP11_1.0.0.1cnot affected

  • AMD AMD Ryzen™ Threadripper™ 9000 Processors

    • ShimadaPeakPI-SP6_1.0.0.1bnot affected

  • AMD AMD Ryzen™ Threadripper™ PRO 9000 WX-Series Processors

    • ShimadaPeakPI-SP6_1.0.0.1bnot affected

  • AMD AMD Ryzen™ Z2 Series Processors Extreme

    • StrixKrackanPI-FP8_1.1.0.0dnot affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12amd64-microcodeall versions—

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-0032Improper cleanup in AMD CPU microcode patch loading could allow an attacker with local administrator privilege to load malicious CPU microco
    28Monitor
  • CVE-2025-0012Improper handling of overlap between the segmented reverse map table (RMP) and system management mode (SMM) memory could allow a privileged
    27Monitor
  • CVE-2025-29952Improper Initialization within the AMD Secure Encrypted Virtualization (SEV) firmware can allow an admin privileged attacker to corrupt RMP
    23Monitor
  • CVE-2025-29948Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass RMP protections,
    23Monitor
  • CVE-2025-52534Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrit
    21Monitor
  • CVE-2025-48517Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES gues
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-1189 · Improper Isolation of Shared Resources on System-on-a-Chip (SoC)

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records