cve.bz

CVE-2023-53087 linux linux kernel

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the barrier deletion. Should the deletion ever fail, we would end up reusing the tracker still registered as a barrier task. Since the same structure field is reused with both fence callback lists and barrier tasks list, list corruptions would likely occur. Barriers are now deleted from a barrier tasks list by temporarily removing the list content, traversing that content with skip over the node to be deleted, then populating the list back with the modified content. Should that intentionally racy concurrent deletion attempts be not serialized, one or more of those may fail because of the list being temporary empty. Related code that ignores the results of barrier deletion was initially introduced in v5.4 by commit d8af05ff38ae ("drm/i915: Allow sharing the idle-barrier from other kernel requests"). However, all users of the barrier deletion routine were apparently serialized at that time, then the issue didn't exhibit itself. Results of git bisect with help of a newly developed igt@gem_barrier_race@remote-request IGT test indicate that list corruptions might start to appear after commit 311770173fac ("drm/i915/gt: Schedule request retirement when timeline idles"), introduced in v5.5. Respect results of barrier deletion attempts -- mark the barrier as idle only if successfully deleted from the list. Then, before proceeding with setting our fence as the one currently tracked, make sure that the tracker we've got is not a non-idle barrier. If that check fails then don't use that tracker but go back and try to acquire a new, usable one. v3: use unlikely() to document what outcome we expect (Andi), - fix bad grammar in commit description. v2: no code changes, - blame commit 311770173fac ("drm/i915/gt: Schedule request retirement when timeline idles"), v5.5, not commit d8af05ff38ae ("drm/i915: Allow sharing the idle-barrier from other kernel requests"), v5.4, - reword commit description. (cherry picked from commit 506006055769b10d1b2b4e22f636f3b45e0e9fc7)

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-53087 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-53087?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-53087?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-53087 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.5 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.176
Linux5.155.15.104
Linux6.16.1.21
Linux6.26.2.8
Linuxlater releases6.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14linux6.1.25-1DEBIAN-CVE-2023-53087
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-53087
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1041.46~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1045.52~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1039.47~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-hwe-5.155.15.0-79.86~20.04.2UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-ibm-5.155.15.0-1036.39~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-intel-iotg-5.155.15.0-1037.42~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-lowlatency-hwe-5.155.15.0-79.88~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-nvidia-tegra-5.155.15.0-1016.16~20.04.1UBUNTU-CVE-2023-53087
Ubuntu20.04:LTSlinux-oracle-5.155.15.0-1040.46~20.04.1UBUNTU-CVE-2023-53087
22 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-513.5.1.el8_9RHSA-2023:7077
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-513.5.1.el8_9RHSA-2023:7077
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 24 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::appstream, enterprise_linux:9::crb, enterprise_linux:9::nfv and 1 morebpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseosbpftool, bpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 41 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 12 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4, Linux Enterprise Micro 5.3 and 1 morekernel-default5.14.21-150400.24.167.1SUSE-SU-2025:02262-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150400.24.167.1SUSE-SU-2025:02262-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 5 morekernel-default-base5.14.21-150400.24.167.1.150400.24.84.1SUSE-SU-2025:02262-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150500.55.110.1SUSE-SU-2025:02173-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.110.1.150500.6.51.3SUSE-SU-2025:02173-1
SUSELinux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_411-150400.9.3.1SUSE-SU-2025:02262-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.110.1SUSE-SU-2025:02173-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_271-150500.11.7.1SUSE-SU-2025:02173-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4kernel-rt, kernel-source-rt5.14.21-150400.15.121.1SUSE-SU-2025:01918-1
SUSELinux Enterprise Micro 5.5kernel-rt, kernel-source-rt5.14.21-150500.13.97.1SUSE-SU-2025:01966-1
SUSELinux Enterprise Micro 5.5kernel-source, kernel-default5.14.21-150500.55.110.1SUSE-SU-2025:02173-1
SUSELinux Enterprise Server 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more5.14.21-150400.24.167.1SUSE-SU-2025:02262-1
5 more for SUSE in the JSON and on SUSE's page.
Alpaquitastreamlinux-lts6.6.58-r0BELL-CVE-2023-53087

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8kernel-0:4.18.0-513.5.1.el8_9Fixed 2023-11-14RHSA-2023:7077
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-53087.

References

Check your stackJSON