cve.bz

CVE-2023-54116 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. 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/fbdev-generic: prohibit potential out-of-bounds access The fbdev test of IGT may write after EOF, which lead to out-of-bound access for drm drivers with fbdev-generic. For example, run fbdev test on a x86+ast2400 platform, with 1680x1050 resolution, will cause the linux kernel hang with the following call trace: Oops: 0000 [#1] PREEMPT SMP PTI [IGT] fbdev: starting subtest eof Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] [IGT] fbdev: starting subtest nullptr RIP: 0010:memcpy_erms+0xa/0x20 RSP: 0018:ffffa17d40167d98 EFLAGS: 00010246 RAX: ffffa17d4eb7fa80 RBX: ffffa17d40e0aa80 RCX: 00000000000014c0 RDX: 0000000000001a40 RSI: ffffa17d40e0b000 RDI: ffffa17d4eb80000 RBP: ffffa17d40167e20 R08: 0000000000000000 R09: ffff89522ecff8c0 R10: ffffa17d4e4c5000 R11: 0000000000000000 R12: ffffa17d4eb7fa80 R13: 0000000000001a40 R14: 000000000000041a R15: ffffa17d40167e30 FS: 0000000000000000(0000) GS:ffff895257380000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffa17d40e0b000 CR3: 00000001eaeca006 CR4: 00000000001706e0 Call Trace: <TASK> ? drm_fbdev_generic_helper_fb_dirty+0x207/0x330 [drm_kms_helper] drm_fb_helper_damage_work+0x8f/0x170 [drm_kms_helper] process_one_work+0x21f/0x430 worker_thread+0x4e/0x3c0 ? __pfx_worker_thread+0x10/0x10 kthread+0xf4/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK> CR2: ffffa17d40e0b000 ---[ end trace 0000000000000000 ]--- The is because damage rectangles computed by drm_fb_helper_memory_range_to_clip() function is not guaranteed to be bound in the screen's active display area. Possible reasons are: 1) Buffers are allocated in the granularity of page size, for mmap system call support. The shadow screen buffer consumed by fbdev emulation may also choosed be page size aligned. 2) The DIV_ROUND_UP() used in drm_fb_helper_memory_range_to_clip() will introduce off-by-one error. For example, on a 16KB page size system, in order to store a 1920x1080 XRGB framebuffer, we need allocate 507 pages. Unfortunately, the size 1920*1080*4 can not be divided exactly by 16KB. 1920 * 1080 * 4 = 8294400 bytes 506 * 16 * 1024 = 8290304 bytes 507 * 16 * 1024 = 8306688 bytes line_length = 1920*4 = 7680 bytes 507 * 16 * 1024 / 7680 = 1081.6 off / line_length = 507 * 16 * 1024 / 7680 = 1081 DIV_ROUND_UP(507 * 16 * 1024, 7680) will yeild 1082 memcpy_toio() typically issue the copy line by line, when copy the last line, out-of-bound access will be happen. Because: 1082 * line_length = 1082 * 7680 = 8309760, and 8309760 > 8306688 Note that userspace may still write to the invisiable area if a larger buffer than width x stride is exposed. But it is not a big issue as long as there still have memory resolve the access if not drafting so far. - Also limit the y1 (Daniel) - keep fix patch it to minimal (Daniel) - screen_size is page size aligned because of it need mmap (Thomas) - Adding fixes tag (Thomas)

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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; 6th 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
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-54116 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-54116?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-54116?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-54116 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.

Badge for a README or a site

CVE-2023-54116

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2023-54116](https://cve.bz/cve/badge/CVE-2023-54116.svg)](https://cve.bz/cve/CVE-2023-54116)

HTML:

<a href="https://cve.bz/cve/CVE-2023-54116"><img src="https://cve.bz/cve/badge/CVE-2023-54116.svg" alt="CVE-2023-54116"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.18 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.30
Linux6.36.3.4
Linuxlater releases6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.37-1DEBIAN-CVE-2023-54116
Debian13, 14linux6.3.7-1DEBIAN-CVE-2023-54116
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-54116
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-54116
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2023-54116
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2023-54116
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 moreno fix listedUBUNTU-CVE-2023-54116
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.133.1SUSE-SU-2026:0317-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.133.1.150500.6.65.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_341-150500.11.3.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Micro 5.5kernel-rt, kernel-source-rt5.14.21-150500.13.118.1SUSE-SU-2026:0263-1
SUSELinux Enterprise Micro 5.5kernel-source, kernel-default5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Server 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 4 more5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Server for SAP Applications 15 SP5kernel-docs, kernel-syms, kernel-source and 2 more5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
Alpaquitastreamlinux-lts6.6.58-r0BELL-CVE-2023-54116

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 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 · SUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low-impact out-of-bounds write was found in the Linux kernel's generic fbdev (framebuffer) emulation used by DRM drivers. When a local user writes past the end of the exposed framebuffer (for example when running the IGT fbdev test), the damage rectangles computed by drm_fb_helper_memory_range_to_clip() are not guaranteed to stay within the screen's active display area: the shadow screen buffer is page-size aligned for mmap support, and an off-by-one from DIV_ROUND_UP() can extend the copied range beyond the end of the buffer. The resulting out-of-bounds access in memcpy_toio() can hang or crash the kernel, causing a local denial of service. Red Hat Enterprise Linux 8 and 9 (kernel and kernel-rt) are affected, and fixes are currently deferred because of the low security impact; the residual risk is limited to a local user triggering a system hang or crash on configurations where the buffer-size rounding error is exposed (specific framebuffer sizes and page sizes). Red Hat Enterprise Linux 6, 7, and 10, and Red Hat In-Vehicle OS 1, are not affected because the vulnerable code is not present in those releases. The Red Hat severity of Low differs from the upstream CVE.org rating of Important (CVSS 7.8) because Red Hat's assessment found only availability impact requiring local access, with no confidentiality or integrity impact.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
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 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
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-54116.

References

Check your stackJSON