mirror of
https://github.com/speed47/spectre-meltdown-checker.git
synced 2026-04-01 12:47:07 +02:00
chore: move dist files to the dist/ subdir
This commit is contained in:
0
Dockerfile → dist/Dockerfile
vendored
0
Dockerfile → dist/Dockerfile
vendored
0
FAQ.md → dist/FAQ.md
vendored
0
FAQ.md → dist/FAQ.md
vendored
0
README.md → dist/README.md
vendored
0
README.md → dist/README.md
vendored
21
dist/UNSUPPORTED_CVE_LIST.md
vendored
Normal file
21
dist/UNSUPPORTED_CVE_LIST.md
vendored
Normal file
@@ -0,0 +1,21 @@
|
|||||||
|
# Unsupported CVEs
|
||||||
|
|
||||||
|
This document lists transient execution CVEs that have been evaluated and determined to be **out of scope** for this tool. See the "CVE Inclusion Criteria" section in [DEVELOPMENT.md](DEVELOPMENT.md) for the general policy.
|
||||||
|
|
||||||
|
## CVE-2024-36348 — AMD Transient Scheduler Attack (UMIP bypass)
|
||||||
|
|
||||||
|
**Bulletin:** [AMD-SB-7029](https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7029.html)
|
||||||
|
**CVSS:** 3.8 (Low)
|
||||||
|
|
||||||
|
A transient execution vulnerability in some AMD processors may allow a user process to speculatively infer CPU configuration registers even when UMIP is enabled.
|
||||||
|
|
||||||
|
**Why out of scope:** AMD has determined that "leakage of CPU Configuration does not result in leakage of sensitive information" and has marked this CVE as "No fix planned" across all affected product lines. No microcode or kernel mitigations have been issued, leaving nothing for this script to check.
|
||||||
|
|
||||||
|
## CVE-2024-36349 — AMD Transient Scheduler Attack (TSC_AUX leak)
|
||||||
|
|
||||||
|
**Bulletin:** [AMD-SB-7029](https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7029.html)
|
||||||
|
**CVSS:** 3.8 (Low)
|
||||||
|
|
||||||
|
A transient execution vulnerability in some AMD processors may allow a user process to infer TSC_AUX even when such a read is disabled.
|
||||||
|
|
||||||
|
**Why out of scope:** AMD has determined that "leakage of TSC_AUX does not result in leakage of sensitive information" and has marked this CVE as "No fix planned" across all affected product lines. No microcode or kernel mitigations have been issued, leaving nothing for this script to check.
|
||||||
Reference in New Issue
Block a user