CVE-2021-26368: Insufficient check of the process type in Trusted OS (TOS) may allow an attacker with privileges to enable a lesser privileged process to…
Noroxi assessment
Priority: Monitor (action score 17/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.14% (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
Insufficient check of the process type in Trusted OS (TOS) may allow an attacker with privileges to enable a lesser privileged process to unmap memory owned by a higher privileged process resulting in a denial of service.
- Published
- May 12, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-345
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| amd | ryzen 3 2200u firmware | cpe:2.3:o:amd:ryzen_3_2200u_firmware |
| amd | ryzen 3 2200u | cpe:2.3:h:amd:ryzen_3_2200u |
| amd | ryzen 3 2300u firmware | cpe:2.3:o:amd:ryzen_3_2300u_firmware |
| amd | ryzen 3 2300u | cpe:2.3:h:amd:ryzen_3_2300u |
| amd | ryzen 3 3100 firmware | cpe:2.3:o:amd:ryzen_3_3100_firmware |
| amd | ryzen 3 3100 | cpe:2.3:h:amd:ryzen_3_3100 |
| amd | ryzen 3 3300g firmware | cpe:2.3:o:amd:ryzen_3_3300g_firmware |
| amd | ryzen 3 3300g | cpe:2.3:h:amd:ryzen_3_3300g |
| amd | ryzen 3 3300x firmware | cpe:2.3:o:amd:ryzen_3_3300x_firmware |
| amd | ryzen 3 3300x | cpe:2.3:h:amd:ryzen_3_3300x |
| amd | ryzen 3 5125c firmware | cpe:2.3:o:amd:ryzen_3_5125c_firmware |
| amd | ryzen 3 5125c | cpe:2.3:h:amd:ryzen_3_5125c |
and 128 more
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 Athlon™ Series
- variousaffected
AMD Ryzen™ Series
- variousaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd ryzen 3 2200u firmwareall versions
- amd ryzen 3 2300u firmwareall versions
- amd ryzen 3 3100 firmwareall versions
- amd ryzen 3 3300g firmwareall versions
- amd ryzen 3 3300x firmwareall versions
- amd ryzen 3 5125c firmwareall versions
- amd ryzen 3 5400u firmwareall versions
- amd ryzen 3 5425c firmwareall versions
- amd ryzen 3 5425u firmwareall versions
- amd ryzen 5 2500u firmwareall versions
- amd ryzen 5 2600 firmwareall versions
- amd ryzen 5 2600h firmwareall versions
- amd ryzen 5 2600x firmwareall versions
- amd ryzen 5 3400g firmwareall versions
- amd ryzen 5 3450g firmwareall versions
- amd ryzen 5 3600 firmwareall versions
- amd ryzen 5 3600x firmwareall versions
- amd ryzen 5 5560u firmwareall versions
- amd ryzen 5 5600h firmwareall versions
- amd ryzen 5 5600hs firmwareall versions
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26386A malicious or compromised UApp or ABL may be used by an attacker to issue a malformed system call to the Stage 2 Bootloader potentially…31Monitor
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- 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
- None
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/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.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (0)
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.