CVE-2022-41804

Unauthorized error injection in Intel(R) SGX or Intel(R) TDX for some Intel(R) Xeon(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

Published: 2023-08-11 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-41804 is rated Low Risk (29.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2022-41804

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 2025-11-21 0.06% 0.01% -0.05%
2 2025-11-18 0.04% 0.06% +0.02%
3 2023-08-11 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-41804

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.2 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:H 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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.6 6.0 [email protected]
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H 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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 5.9 [email protected]

Weakness enumeration for CVE-2022-41804

OS Trackers for CVE-2022-41804

vendor priority summary link
alpine medium CVE-2022-41804: 1 source package rows (intel-ucode); 7 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2022-41804
debian not yet assigned CVE-2022-41804 not yet assigned priority: Debian including 1 source packages (intel-microcode), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-41804
redhat high — https://access.redhat.com/security/cve/CVE-2022-41804
suse high CVE-2022-41804 severity important: SUSE including 9 source package names (microcode_ctl-1.17-102.83.81.1, ucode-intel-20230808-1.1, …), 57 product×package rows across 57 product lines (Image SLES12-SP5-SAP-Azure-LI-BYOS-Production, Image SLES12-SP5-SAP-Azure-VLI-BYOS-Production, … (57 product lines)): Fixed 57. https://www.suse.com/security/cve/CVE-2022-41804/
ubuntu medium CVE-2022-41804 medium priority: Ubuntu including 1 source packages (intel-microcode), 10 status rows across 10 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, trusty, upstream, xenial): released 8, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2022-41804

Affected software / configurations for CVE-2022-41804

Vendor Product Version Raw CPE
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
debian debian_linux 12.0 cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*
intel xeon_gold_5315y_firmware — cpe:2.3:o:intel:xeon_gold_5315y_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5317_firmware — cpe:2.3:o:intel:xeon_gold_5317_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5318n_firmware — cpe:2.3:o:intel:xeon_gold_5318n_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5318s_firmware — cpe:2.3:o:intel:xeon_gold_5318s_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5318y_firmware — cpe:2.3:o:intel:xeon_gold_5318y_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5320_firmware — cpe:2.3:o:intel:xeon_gold_5320_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5320t_firmware — cpe:2.3:o:intel:xeon_gold_5320t_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6312u_firmware — cpe:2.3:o:intel:xeon_gold_6312u_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6314u_firmware — cpe:2.3:o:intel:xeon_gold_6314u_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6326_firmware — cpe:2.3:o:intel:xeon_gold_6326_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6330_firmware — cpe:2.3:o:intel:xeon_gold_6330_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6330n_firmware — cpe:2.3:o:intel:xeon_gold_6330n_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6334_firmware — cpe:2.3:o:intel:xeon_gold_6334_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6336y_firmware — cpe:2.3:o:intel:xeon_gold_6336y_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6338_firmware — cpe:2.3:o:intel:xeon_gold_6338_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6338n_firmware — cpe:2.3:o:intel:xeon_gold_6338n_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6338t_firmware — cpe:2.3:o:intel:xeon_gold_6338t_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6342_firmware — cpe:2.3:o:intel:xeon_gold_6342_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6346_firmware — cpe:2.3:o:intel:xeon_gold_6346_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6348_firmware — cpe:2.3:o:intel:xeon_gold_6348_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6354_firmware — cpe:2.3:o:intel:xeon_gold_6354_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8351n_firmware — cpe:2.3:o:intel:xeon_platinum_8351n_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8352m_firmware — cpe:2.3:o:intel:xeon_platinum_8352m_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8352s_firmware — cpe:2.3:o:intel:xeon_platinum_8352s_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8352v_firmware — cpe:2.3:o:intel:xeon_platinum_8352v_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8352y_firmware — cpe:2.3:o:intel:xeon_platinum_8352y_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8358_firmware — cpe:2.3:o:intel:xeon_platinum_8358_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8358p_firmware — cpe:2.3:o:intel:xeon_platinum_8358p_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8360y_firmware — cpe:2.3:o:intel:xeon_platinum_8360y_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8362_firmware — cpe:2.3:o:intel:xeon_platinum_8362_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8368_firmware — cpe:2.3:o:intel:xeon_platinum_8368_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8368q_firmware — cpe:2.3:o:intel:xeon_platinum_8368q_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8380_firmware — cpe:2.3:o:intel:xeon_platinum_8380_firmware:-:*:*:*:*:*:*:*
intel xeon_silver_4309y_firmware — cpe:2.3:o:intel:xeon_silver_4309y_firmware:-:*:*:*:*:*:*:*
intel xeon_silver_4310_firmware — cpe:2.3:o:intel:xeon_silver_4310_firmware:-:*:*:*:*:*:*:*
intel xeon_silver_4310t_firmware — cpe:2.3:o:intel:xeon_silver_4310t_firmware:-:*:*:*:*:*:*:*
intel xeon_silver_4314_firmware — cpe:2.3:o:intel:xeon_silver_4314_firmware:-:*:*:*:*:*:*:*
intel xeon_silver_4316_firmware — cpe:2.3:o:intel:xeon_silver_4316_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6330h_firmware — cpe:2.3:o:intel:xeon_gold_6330h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8356h_firmware — cpe:2.3:o:intel:xeon_platinum_8356h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8360h_firmware — cpe:2.3:o:intel:xeon_platinum_8360h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8360hl_firmware — cpe:2.3:o:intel:xeon_platinum_8360hl_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5318h_firmware — cpe:2.3:o:intel:xeon_gold_5318h_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_5320h_firmware — cpe:2.3:o:intel:xeon_gold_5320h_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6328h_firmware — cpe:2.3:o:intel:xeon_gold_6328h_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6328hl_firmware — cpe:2.3:o:intel:xeon_gold_6328hl_firmware:-:*:*:*:*:*:*:*
intel xeon_gold_6348h_firmware — cpe:2.3:o:intel:xeon_gold_6348h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8353h_firmware — cpe:2.3:o:intel:xeon_platinum_8353h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8354h_firmware — cpe:2.3:o:intel:xeon_platinum_8354h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8376h_firmware — cpe:2.3:o:intel:xeon_platinum_8376h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8376hl_firmware — cpe:2.3:o:intel:xeon_platinum_8376hl_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8380h_firmware — cpe:2.3:o:intel:xeon_platinum_8380h_firmware:-:*:*:*:*:*:*:*
intel xeon_platinum_8380hl_firmware — cpe:2.3:o:intel:xeon_platinum_8380hl_firmware:-:*:*:*:*:*:*:*
intel xeon_d-2745nx_firmware — cpe:2.3:o:intel:xeon_d-2745nx_firmware:-:*:*:*:*:*:*:*
intel xeon_d-2757nx_firmware — cpe:2.3:o:intel:xeon_d-2757nx_firmware:-:*:*:*:*:*:*:*
intel xeon_d-2777nx_firmware — cpe:2.3:o:intel:xeon_d-2777nx_firmware:-:*:*:*:*:*:*:*
intel xeon_d-2798nx_firmware — cpe:2.3:o:intel:xeon_d-2798nx_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1702_firmware — cpe:2.3:o:intel:xeon_d-1702_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1712tr_firmware — cpe:2.3:o:intel:xeon_d-1712tr_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1713nt_firmware — cpe:2.3:o:intel:xeon_d-1713nt_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1713nte_firmware — cpe:2.3:o:intel:xeon_d-1713nte_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1714_firmware — cpe:2.3:o:intel:xeon_d-1714_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1715ter_firmware — cpe:2.3:o:intel:xeon_d-1715ter_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1718t_firmware — cpe:2.3:o:intel:xeon_d-1718t_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1722ne_firmware — cpe:2.3:o:intel:xeon_d-1722ne_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1726_firmware — cpe:2.3:o:intel:xeon_d-1726_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1732te_firmware — cpe:2.3:o:intel:xeon_d-1732te_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1733nt_firmware — cpe:2.3:o:intel:xeon_d-1733nt_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1734nt_firmware — cpe:2.3:o:intel:xeon_d-1734nt_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1735tr_firmware — cpe:2.3:o:intel:xeon_d-1735tr_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1736_firmware — cpe:2.3:o:intel:xeon_d-1736_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1736nt_firmware — cpe:2.3:o:intel:xeon_d-1736nt_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1739_firmware — cpe:2.3:o:intel:xeon_d-1739_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1746ter_firmware — cpe:2.3:o:intel:xeon_d-1746ter_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1747nte_firmware — cpe:2.3:o:intel:xeon_d-1747nte_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1748te_firmware — cpe:2.3:o:intel:xeon_d-1748te_firmware:-:*:*:*:*:*:*:*
intel xeon_d-1749nt_firmware — cpe:2.3:o:intel:xeon_d-1749nt_firmware:-:*:*:*:*:*:*:*

References for CVE-2022-41804

cvelogic Threat Intelligence