CVE-2023-52931 | drm/i915: Avoid potential vm use-after-free

In the Linux kernel, the following vulnerability has been resolved: drm/i915: Avoid potential vm use-after-free Adding the vm to the vm_xa table makes it visible to userspace, which could try to race with us to close the vm. So we need to take our extra reference before putting it in the table. (cherry picked from commit 99343c46d4e2b34c285d3d5f68ff04274c2f9fb4)

Published: 2025-03-27 Last update: 2025-04-01 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-52931 is rated Low Risk (39.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.08%). 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-52931

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-05-05 0.02% 0.08% +0.06%
2 2025-03-28 — 0.02% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/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: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: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.
 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-52931

OS Trackers for CVE-2023-52931

vendor priority summary link
debian unimportant CVE-2023-52931 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-52931
redhat medium — https://access.redhat.com/security/cve/CVE-2023-52931
suse medium — https://www.suse.com/security/cve/CVE-2023-52931/
ubuntu medium CVE-2023-52931 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 117, released 64. https://ubuntu.com/security/CVE-2023-52931

Affected software / configurations for CVE-2023-52931

Vendor Product Version Raw CPE
linux linux_kernel >= 5.16, < 6.1.11 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc1:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc2:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc3:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc4:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc5:*:*:*:*:*:*
linux linux_kernel 6.2 cpe:2.3:o:linux:linux_kernel:6.2:rc6:*:*:*:*:*:*

References for CVE-2023-52931

cvelogic Threat Intelligence