vciy

CVE-2025-48502

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Improper input validation within AMD uprof can allow a local attacker to overwrite MSR registers, potentially resulting in crash or denial of service.

CVE-2025-485024 of 4 sources documented this
19

rank 19 = 0 + 14 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00110  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.5, from the CNA  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 19

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 14

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 19

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3,360over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$3,360 = $4.99M incident cost x 0.6121449559255632 exposure x 0.0011 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.0011EPSSNOT IN KEVas of 2026-09-20
Severity5.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-11-22, 268 days at 0.00, as of 2026-08-17. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running AMD μProf? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-1285 Improper Validation of Specified Index, Position, or Offset in Inputreceipt
Published consequencesCWE-1285: Other: Varies by Context[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in5.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA5.5 MEDIUMreceipt
Exploit probability0.0011 · top 99% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byAMDreceipt
Recorded changes13 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productAMD μProfreceipt
Published rangesamd uprof < 5.0.1174; amd uprof < 5.0.1223; amd uprof < 5.0.1479receipt
Fixed in5.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Local accessrequires low privilegesAMD μProfCWE-1285 weaknessAvailability lossA:Hexploits CWE-1285data compromise

What it is stated by the CNA

Improper input validation within AMD uprof can allow a local attacker to overwrite MSR registers, potentially resulting in crash or denial of service. receipt

NVD's analysis a second authority

weakness
CWE-1285
affected versions
amd uprof < 5.0.1174; amd uprof < 5.0.1223; amd uprof < 5.0.1479
also scored by
[email protected] 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

check it yourself amd.com receipt

Movement the material steps

22 Nov 20250.00014
15 Jun 20260.00095 · scoring model v2026.06.15
17 Aug 20260.0011
Show all 13 observations
22 Nov 20250.00014
27 Nov 20250.00016
23 Dec 20250.00019
28 Jan 20260.00022
23 Mar 20260.00049
19 Apr 20260.00032
20 Apr 20260.00031
1 May 20260.00032
15 Jun 20260.00095
20 Jun 20260.00097
10 Jul 20260.00099
19 Jul 20260.00108
17 Aug 20260.0011

13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.0011Published2025-11-21Index as of2026-08-17

The record had been public for 8 months when this index was last written.

Published 2025-11-21 receipt · Index as of 2026-08-17 derived

Siblings and hubs

Records related to this one

Its defect family

amd μprof

Of the 4 records in this advisory that state one, this holds the lowest EPSS percentile: 0.01418.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-48502.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.