CVE-2023-46103

Sequence of processor instructions leads to unexpected behavior in Intel(R) Core(TM) Ultra Processors may allow an authenticated user to potentially enable denial of service via local access.

Published: 2024-05-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-46103 is rated Low Risk (25.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.28%). 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-2023-46103

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.01% 0.28% +0.27%
2 2025-11-21 0.06% 0.01% -0.05%
3 2025-11-18 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-46103

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:L)
A normal user session is enough; they don’t have to be admin.
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:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 3.6 [email protected]

Weakness enumeration for CVE-2023-46103

OS Trackers for CVE-2023-46103

vendor priority summary link
alpine medium CVE-2023-46103: 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-2023-46103
debian not yet assigned CVE-2023-46103 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-2023-46103
redhat medium — https://access.redhat.com/security/cve/CVE-2023-46103
suse high CVE-2023-46103 severity important: SUSE including 9 source package names (microcode_ctl-1.17-102.83.81.1, microcode_ctl-20240910-1.el9_5, …), 56 product×package rows across 56 product lines (Image SLES12-SP5-SAP-Azure-LI-BYOS-Production, Image SLES12-SP5-SAP-Azure-VLI-BYOS-Production, … (56 product lines)): Fixed 56. https://www.suse.com/security/cve/CVE-2023-46103/
ubuntu medium CVE-2023-46103 medium priority: Ubuntu including 1 source packages (intel-microcode), 8 status rows across 8 suites (bionic, focal, jammy, mantic, noble, trusty, upstream, xenial): released 6, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2023-46103

Affected software / configurations for CVE-2023-46103

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2023-46103

cvelogic Threat Intelligence