CVE-2026-72089
Received Received - Intake

BaseFortify

Publication date: 2026-08-15

Last updated on: 2026-08-15

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Reject firmware log with size smaller than header fw_log_from_bo() validates the tracing buffer header_size and that the log fits within the BO, but never checks that log->size is at least log->header_size. fw_log_print_buffer() then computes: u32 data_size = log->size - log->header_size; which underflows to a near-U32_MAX value when firmware reports a log whose size is smaller than its header. That huge data_size defeats the log_start/log_end bounds clamps added by commit dd1311bcf0e6 ("accel/ivpu: Add bounds checks for firmware log indices"), so fw_log_print_lines() reads far past the small real data region of the BO. A size of 0 also makes fw_log_from_bo() advance the offset by 0, causing the callers to loop forever on the same header. Reject logs whose size is smaller than the header (which also rejects size == 0).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-15
Generated
2026-08-15
AI Q&A
2026-08-15
EPSS Evaluated
N/A
NVD
CVE-2026-72089
EUVD
EUVD-2026-59047

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in the Linux kernel's accel/ivpu component. It involves improper validation of firmware log size. The function fw_log_from_bo() fails to check if the log size is at least as large as the header size. This causes an integer underflow when calculating data_size, leading to reading outside the intended memory region. It also allows infinite loops if the size is zero.

Detection Guidance

This vulnerability is specific to the Linux kernel's accel/ivpu driver and requires kernel-level inspection. Detection involves checking kernel logs for firmware log parsing errors or unusual behavior in the ivpu driver. Commands like dmesg | grep ivpu or journalctl -k | grep ivpu may reveal issues. No network-specific detection commands are applicable.

Impact Analysis

This vulnerability could allow a local attacker with access to the system to cause a denial of service or potentially execute arbitrary code in the kernel. It may lead to system crashes, data corruption, or privilege escalation if exploited.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for this vulnerability. Monitor kernel logs for ivpu-related errors after updating. If immediate patching is not possible, consider disabling the ivpu driver if not in use, but this may impact functionality.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72089. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart