CVE-2026-80741: drm/log: Fix out-of-bounds read on empty message length
In the Linux kernel, the following vulnerability has been resolved:
drm/log: Fix out-of-bounds read on empty message length
drmlogdrawkmsgrecord() accesses s[len - 1] to strip the trailing newline, but len is unsigned int. If len is 0, the subtraction wraps to UINTMAX, causing an out-of-bounds read.
Add an early return when len is 0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Compensating control
In drm_log_draw_kmsg_record(), add an early return when len is 0 before accessing s[len - 1].
Event History
Frequently Asked Questions
Can exposure be determined from the kernel version alone?
No affected kernel version range is provided. The available references point to stable-kernel fixes, so deployments should compare their kernel source or applied patches with those fixes.
What runtime condition reaches the vulnerable access?
The issue occurs when drm_log_draw_kmsg_record() handles a message whose length is zero. The unsigned length value underflows during len - 1, causing an out-of-bounds read.
What does the available fix change?
The fix adds an early return when the message length is zero, preventing the underflowing index calculation and subsequent read.