Skip to content
Noroxi
NVD / CVE Program· CNA AMD

CVE-2021-26367: A malicious attacker in x86 can misconfigure the Trusted Memory Regions (TMRs), which may allow the attacker to set an arbitrary address ran

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A malicious attacker in x86 can misconfigure the Trusted Memory Regions (TMRs), which may allow the attacker to set an arbitrary address range for the TMR, potentially leading to a loss of integrity and availability.

MediumCVSS 6.0 · v3.1—No exploit No fix recorded
Published
Aug 13, 2024
Updated
Jun 16, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.0 / 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
6.0
CNA · AMD
5.7
0.3 point gap

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H

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

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-26367

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amdradeon software
amdradeon rx 6300m
amdradeon rx 6400
amdradeon rx 6450m
amdradeon rx 6500 xt
amdradeon rx 6500m
amdradeon rx 6550m
amdradeon rx 6550s
amdradeon rx 6600
amdradeon rx 6600 xt
amdradeon rx 6600m
amdradeon rx 6600s

and 90 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amd athlon gold 3150c firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon gold 3150g firmwarebefore comboam4pi_1.0.0.9
  • amd athlon gold 3150u firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon gold pro 3150g firmwarebefore comboam4pi_1.0.0.9
  • amd athlon gold pro 3150ge firmwarebefore comboam4pi_1.0.0.9
  • amd athlon pro 300ge firmwarebefore comboam4pi_1.0.0.9
  • amd athlon pro 3045b firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon pro 3145b firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon silver 3050c firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon silver 3050e firmwarebefore picassopi-fp5_1.0.0.e
  • amd athlon silver 3050u firmwarebefore picassopi-fp5_1.0.0.e
  • amd radeon softwarebefore 23.12.1
  • amd radeon softwareup to 23.q4 inclusive
  • amd ryzen 3 3300u firmwarebefore picassopi-fp5_1.0.0.e
  • amd ryzen 3 3350u firmwarebefore picassopi-fp5_1.0.0.e
  • amd ryzen 3 4300g firmwarebefore comboam4v2_pi_1.2.0.5
  • amd ryzen 3 4300ge firmwarebefore comboam4v2_pi_1.2.0.5
  • amd ryzen 3 5300g firmwarebefore comboam4v2_pi_1.2.0.5
  • amd ryzen 3 5300ge firmwarebefore comboam4v2_pi_1.2.0.5
  • amd ryzen 5 3450u firmwarebefore picassopi-fp5_1.0.0.e

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 Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics

    • ComboAM4PI 1.0.0.9, ComboAM4v2 PI 1.2.0.8not affected
  • AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics

    • PicassoPI-FP5 1.0.0.E, PollockPI-FT5 1.0.0.4not affected
  • AMD AMD Radeon™ PRO W6000 Series Graphics Cards

    • AMD Software: PRO Edition 23.Q4 (23.30.13.03)not affected
  • AMD AMD Radeon™ RX 6000 Series Graphics Cards

    • AMD Software: Adrenalin Edition 23.12.1 (23.30.13.01)not affected
  • AMD AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics

    • PicassoPI-FP5 1.0.0.Enot affected
  • AMD AMD Ryzen™ 3000 Series Processors with Radeon™ Graphics

    • CezannePI-FP6 1.0.0.6, CezannePI-FP6 1.0.0.6not affected
  • AMD AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics

    • ComboAM4v2 PI 1.2.0.5not affected
  • AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics

    • RenoirPI-FP6 1.0.0.7not affected
  • AMD AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics

    • ComboAM4v2 PI 1.2.0.5not affected
  • AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics

    • CezannePI-FP6 1.0.0.6not affected
  • AMD AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics

    • CezannePI-FP6 1.0.0.6, CezannePI-FP6 1.0.0.6not affected
  • AMD AMD Ryzen™ Embedded R1000 Series Processors

    • EmbeddedPI-FP5 1.2.0.Anot affected

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-20586Radeon™ Software Crimson ReLive Edition
    39Monitor
  • CVE-2024-21937Incorrect default permissions in the AMD HIP SDK installation directory could allow an attacker to achieve privilege escalation potentially
    31Monitor
  • CVE-2023-20598 An improper privilege management in the AMD Radeon™ Graphics driver may allow an authenticated attacker to craft an IOCTL request to gain
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-20567Nov 14, 2023 · Improper signature verification of RadeonTM RX Vega M Graphics driver for Windows may allow an attacker with admin privileges to launch AMDS
    26Monitor
  • ← EarlierCVE-2023-31320Nov 14, 2023 · Improper input validation in the AMD RadeonTM Graphics display driver may allow an attacker to corrupt the display potentially resulting in
    30Monitor
  • Later →CVE-2023-20510Aug 13, 2024 · An insufficient DRAM address validation in PMFW may allow a privileged attacker to read from an invalid DRAM address to SRAM, potentially re
    24Monitor

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.

No history yet (it accumulates with the daily EPSS job).

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.

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.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

nvd-primary

Attack context

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

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

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

References

Show all references (1 more)

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

All records