{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-80741","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-08-26T14:34:25.790Z","datePublished":"2026-09-03T08:26:25.322Z","dateUpdated":"2026-09-04T04:58:24.919Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-09-04T04:58:24.919Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/log: Fix out-of-bounds read on empty message length\n\ndrm_log_draw_kmsg_record() accesses s[len - 1] to strip the trailing\nnewline, but len is unsigned int. If len is 0, the subtraction wraps\nto UINT_MAX, causing an out-of-bounds read.\n\nAdd an early return when len is 0."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","baseScore":7.1,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The bug is in drm_log, an in-kernel DRM boot console that renders printk records to the framebuffer; it is only reached from the local printk/nbcon console path, not from any network protocol or physical bus.\nAC:L - Once CONFIG_DRM_CLIENT_LOG is active (common on embedded/kiosk displays), a local actor can drive printk/console output; if a zero-length record is delivered to drm_log_draw_kmsg_record(), the unsigned wrap to UINT_MAX makes the OOB read deterministic rather than race-dependent.\nPR:L - No root or DRM master is required to reach the console printk path; unprivileged local processes routinely trigger kernel logging via syscalls and /dev/kmsg (CAP_SYSLOG is obtainable in user namespaces), and drm_log only refuses to draw when a userspace DRM master is already held.\nUI:N - Exploitation does not require any victim to click, mount, or open a file; it is triggered automatically when the kernel console layer emits a qualifying (including zero-length) message to the drm_log nbcon handler.\nS:U - Impact stays within kernel context on the same machine (display logger crash/OOB read); it does not cross a VM, container, or IOMMU security boundary.\nC:H - With len=0, s[len-1] indexes s[UINT_MAX-1], an unbounded out-of-bounds kernel read; per kernel CVSS guidance, OOB reads are rated High even when the immediate fault dominates.\nI:N - The defect is a read-side integer underflow only; it does not corrupt or write adjacent memory and provides no direct arbitrary-write or code-execution primitive.\nA:H - Reading at offset UINT_MAX from the printk outbuf is virtually certain to fault the console thread with a kernel oops/panic, denying display and potentially halting the system on embedded drm_log deployments."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/clients/drm_log.c"],"versions":[{"version":"25e2c2a3eff55683bbe77b108db2a7e389246666","lessThan":"16a2716910ecf7d31bf3c033ee7c506a0b00b2ee","status":"affected","versionType":"git"},{"version":"25e2c2a3eff55683bbe77b108db2a7e389246666","lessThan":"16bcea56f4205314ec2aa04a7ec74e5261d253c7","status":"affected","versionType":"git"},{"version":"25e2c2a3eff55683bbe77b108db2a7e389246666","lessThan":"60baa179ed1333535f6e2da4133511db55278ee4","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/clients/drm_log.c"],"versions":[{"version":"6.14","status":"affected"},{"version":"0","lessThan":"6.14","status":"unaffected","versionType":"semver"},{"version":"6.18.46","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.1.10","lessThanOrEqual":"7.1.*","status":"unaffected","versionType":"semver"},{"version":"7.2","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"6.18.46"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"7.1.10"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"7.2"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/16a2716910ecf7d31bf3c033ee7c506a0b00b2ee"},{"url":"https://git.kernel.org/stable/c/16bcea56f4205314ec2aa04a7ec74e5261d253c7"},{"url":"https://git.kernel.org/stable/c/60baa179ed1333535f6e2da4133511db55278ee4"}],"title":"drm/log: Fix out-of-bounds read on empty message length","x_generator":{"engine":"bippy-1.2.0"}}}}