CVE-2021-1125

NVIDIA GPU and Tegra hardware contain a vulnerability in the internal microcontroller which may allow a user with elevated privileges to corrupt program data.

Published: 2021-11-20 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2021-1125 is rated Low Risk (19.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-1125

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.19% +0.14%
2 2025-03-30 0.06% 0.05% -0.01%
3 2025-03-29 — 0.06% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-1125

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.1 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 0.5 3.6 [email protected]
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 [email protected]
4.9 2.0 MEDIUM
AV:L/AC:L/Au:N/C:N/I:C/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:N)
No availability impact.
 3.9 6.9 [email protected]

Weakness enumeration for CVE-2021-1125

Affected software / configurations for CVE-2021-1125

Vendor Product Version Raw CPE
nvidia dgx-1_p100 — cpe:2.3:h:nvidia:dgx-1_p100:-:*:*:*:*:*:*:*
nvidia dgx-1_v100 — cpe:2.3:h:nvidia:dgx-1_v100:-:*:*:*:*:*:*:*
nvidia dgx-2 — cpe:2.3:h:nvidia:dgx-2:-:*:*:*:*:*:*:*
nvidia dgx_station_a100 — cpe:2.3:h:nvidia:dgx_station_a100:-:*:*:*:*:*:*:*
nvidia geforce_gt_605 — cpe:2.3:h:nvidia:geforce_gt_605:-:*:*:*:*:*:*:*
nvidia geforce_gt_610 — cpe:2.3:h:nvidia:geforce_gt_610:-:*:*:*:*:*:*:*
nvidia geforce_gt_620 — cpe:2.3:h:nvidia:geforce_gt_620:-:*:*:*:*:*:*:*
nvidia geforce_gt_625 — cpe:2.3:h:nvidia:geforce_gt_625:-:*:*:*:*:*:*:*
nvidia geforce_gt_630 — cpe:2.3:h:nvidia:geforce_gt_630:-:*:*:*:*:*:*:*
nvidia geforce_gt_635 — cpe:2.3:h:nvidia:geforce_gt_635:-:*:*:*:*:*:*:*
nvidia geforce_gt_640 — cpe:2.3:h:nvidia:geforce_gt_640:-:*:*:*:*:*:*:*
nvidia geforce_gt_705 — cpe:2.3:h:nvidia:geforce_gt_705:-:*:*:*:*:*:*:*
nvidia geforce_gt_710 — cpe:2.3:h:nvidia:geforce_gt_710:-:*:*:*:*:*:*:*
nvidia geforce_gt_720 — cpe:2.3:h:nvidia:geforce_gt_720:-:*:*:*:*:*:*:*
nvidia geforce_gt_730 — cpe:2.3:h:nvidia:geforce_gt_730:-:*:*:*:*:*:*:*
nvidia geforce_gt_740 — cpe:2.3:h:nvidia:geforce_gt_740:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1050 — cpe:2.3:h:nvidia:geforce_gtx_1050:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1050_ti — cpe:2.3:h:nvidia:geforce_gtx_1050_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1060 — cpe:2.3:h:nvidia:geforce_gtx_1060:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1070 — cpe:2.3:h:nvidia:geforce_gtx_1070:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1070_ti — cpe:2.3:h:nvidia:geforce_gtx_1070_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1080 — cpe:2.3:h:nvidia:geforce_gtx_1080:-:*:*:*:*:*:*:*
nvidia geforce_gtx_1080_ti — cpe:2.3:h:nvidia:geforce_gtx_1080_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_645 — cpe:2.3:h:nvidia:geforce_gtx_645:-:*:*:*:*:*:*:*
nvidia geforce_gtx_650 — cpe:2.3:h:nvidia:geforce_gtx_650:-:*:*:*:*:*:*:*
nvidia geforce_gtx_650_ti — cpe:2.3:h:nvidia:geforce_gtx_650_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_650_ti_boost — cpe:2.3:h:nvidia:geforce_gtx_650_ti_boost:-:*:*:*:*:*:*:*
nvidia geforce_gtx_660 — cpe:2.3:h:nvidia:geforce_gtx_660:-:*:*:*:*:*:*:*
nvidia geforce_gtx_660_ti — cpe:2.3:h:nvidia:geforce_gtx_660_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_670 — cpe:2.3:h:nvidia:geforce_gtx_670:-:*:*:*:*:*:*:*
nvidia geforce_gtx_680 — cpe:2.3:h:nvidia:geforce_gtx_680:-:*:*:*:*:*:*:*
nvidia geforce_gtx_690 — cpe:2.3:h:nvidia:geforce_gtx_690:-:*:*:*:*:*:*:*
nvidia geforce_gtx_745 — cpe:2.3:h:nvidia:geforce_gtx_745:-:*:*:*:*:*:*:*
nvidia geforce_gtx_750 — cpe:2.3:h:nvidia:geforce_gtx_750:-:*:*:*:*:*:*:*
nvidia geforce_gtx_750_ti — cpe:2.3:h:nvidia:geforce_gtx_750_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_760 — cpe:2.3:h:nvidia:geforce_gtx_760:-:*:*:*:*:*:*:*
nvidia geforce_gtx_760_ti — cpe:2.3:h:nvidia:geforce_gtx_760_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_770 — cpe:2.3:h:nvidia:geforce_gtx_770:-:*:*:*:*:*:*:*
nvidia geforce_gtx_780 — cpe:2.3:h:nvidia:geforce_gtx_780:-:*:*:*:*:*:*:*
nvidia geforce_gtx_780_ti — cpe:2.3:h:nvidia:geforce_gtx_780_ti:-:*:*:*:*:*:*:*
nvidia geforce_gtx_950 — cpe:2.3:h:nvidia:geforce_gtx_950:-:*:*:*:*:*:*:*
nvidia geforce_gtx_960 — cpe:2.3:h:nvidia:geforce_gtx_960:-:*:*:*:*:*:*:*
nvidia geforce_gtx_970 — cpe:2.3:h:nvidia:geforce_gtx_970:-:*:*:*:*:*:*:*
nvidia geforce_gtx_980 — cpe:2.3:h:nvidia:geforce_gtx_980:-:*:*:*:*:*:*:*
nvidia geforce_gtx_titan_x — cpe:2.3:h:nvidia:geforce_gtx_titan_x:-:*:*:*:*:*:*:*
nvidia gtx_titan — cpe:2.3:h:nvidia:gtx_titan:-:*:*:*:*:*:*:*
nvidia gtx_titan_black — cpe:2.3:h:nvidia:gtx_titan_black:-:*:*:*:*:*:*:*
nvidia gtx_titan_z — cpe:2.3:h:nvidia:gtx_titan_z:-:*:*:*:*:*:*:*
nvidia jetson_agx_xavier_16gb — cpe:2.3:h:nvidia:jetson_agx_xavier_16gb:-:*:*:*:*:*:*:*
nvidia jetson_agx_xavier_32gb — cpe:2.3:h:nvidia:jetson_agx_xavier_32gb:-:*:*:*:*:*:*:*
nvidia jetson_agx_xavier_8gb — cpe:2.3:h:nvidia:jetson_agx_xavier_8gb:-:*:*:*:*:*:*:*
nvidia jetson_nano — cpe:2.3:h:nvidia:jetson_nano:-:*:*:*:*:*:*:*
nvidia jetson_nano — cpe:2.3:h:nvidia:jetson_nano:-:*:-:*:*:*:*:*
nvidia jetson_nano — cpe:2.3:h:nvidia:jetson_nano:-:*:developer_kit:*:*:*:*:*
nvidia jetson_tx1 — cpe:2.3:h:nvidia:jetson_tx1:-:*:*:*:*:*:*:*
nvidia jetson_tx2 — cpe:2.3:h:nvidia:jetson_tx2:-:*:*:*:*:*:*:*
nvidia jetson_tx2_4gb — cpe:2.3:h:nvidia:jetson_tx2_4gb:-:*:*:*:*:*:*:*
nvidia jetson_tx2_nx — cpe:2.3:h:nvidia:jetson_tx2_nx:-:*:*:*:*:*:*:*
nvidia jetson_tx2i — cpe:2.3:h:nvidia:jetson_tx2i:-:*:*:*:*:*:*:*
nvidia jetson_xavier_nx — cpe:2.3:h:nvidia:jetson_xavier_nx:-:*:*:*:*:*:*:*
nvidia jetson_xavier_nx — cpe:2.3:h:nvidia:jetson_xavier_nx:-:*:developer_kit:*:*:*:*:*
nvidia jetson_xavier_nx — cpe:2.3:h:nvidia:jetson_xavier_nx:-:*:production:*:*:*:*:*
nvidia nvidia_hgx-2 — cpe:2.3:h:nvidia:nvidia_hgx-2:-:*:*:*:*:*:*:*
nvidia quadro_gv100 — cpe:2.3:h:nvidia:quadro_gv100:-:*:*:*:*:*:*:*
nvidia quadro_m1000m — cpe:2.3:h:nvidia:quadro_m1000m:-:*:*:*:*:*:*:*
nvidia quadro_m1200 — cpe:2.3:h:nvidia:quadro_m1200:-:*:*:*:*:*:*:*
nvidia quadro_m2000 — cpe:2.3:h:nvidia:quadro_m2000:-:*:*:*:*:*:*:*
nvidia quadro_m2000m — cpe:2.3:h:nvidia:quadro_m2000m:-:*:*:*:*:*:*:*
nvidia quadro_m2200 — cpe:2.3:h:nvidia:quadro_m2200:-:*:*:*:*:*:*:*
nvidia quadro_m3000m — cpe:2.3:h:nvidia:quadro_m3000m:-:*:*:*:*:*:*:*
nvidia quadro_m4000 — cpe:2.3:h:nvidia:quadro_m4000:-:*:*:*:*:*:*:*
nvidia quadro_m4000m — cpe:2.3:h:nvidia:quadro_m4000m:-:*:*:*:*:*:*:*
nvidia quadro_m5000 — cpe:2.3:h:nvidia:quadro_m5000:-:*:*:*:*:*:*:*
nvidia quadro_m5000m — cpe:2.3:h:nvidia:quadro_m5000m:-:*:*:*:*:*:*:*
nvidia quadro_m500m — cpe:2.3:h:nvidia:quadro_m500m:-:*:*:*:*:*:*:*
nvidia quadro_m520 — cpe:2.3:h:nvidia:quadro_m520:-:*:*:*:*:*:*:*
nvidia quadro_m5500 — cpe:2.3:h:nvidia:quadro_m5500:-:*:*:*:*:*:*:*
nvidia quadro_m6000 — cpe:2.3:h:nvidia:quadro_m6000:-:*:*:*:*:*:*:*
nvidia quadro_m600m — cpe:2.3:h:nvidia:quadro_m600m:-:*:*:*:*:*:*:*
nvidia quadro_m620 — cpe:2.3:h:nvidia:quadro_m620:-:*:*:*:*:*:*:*

References for CVE-2021-1125

cvelogic Threat Intelligence