Skip to main content

Linux Kernel CVE-2026-72089

| EUVDEUVD-2026-59047 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-f4rx-vf72-pg97
7.1
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
vuln.today AI
7.1 HIGH

Local driver interface, low-privilege access sufficient; C:H for kernel OOB read disclosure, A:H for infinite loop DoS; no integrity impact confirmed from description.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
6.1 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 06:44 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.1 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.1
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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).

AnalysisAI

Integer underflow in the Linux kernel's Intel VPU accelerator driver (accel/ivpu) allows a local low-privileged attacker to trigger out-of-bounds kernel memory reads and infinite loops via a malformed firmware log buffer. The vulnerability exists because fw_log_from_bo() never validates that log->size is at least log->header_size before fw_log_print_buffer() computes data_size = log->size - log->header_size - a u32 subtraction that wraps to near-U32_MAX, defeating the bounds checks from commit dd1311bcf0e6 and enabling fw_log_print_lines() to read far past the allocated BO region. No active exploitation is confirmed (not in CISA KEV), and EPSS is 0.21% (11th percentile), indicating low near-term exploitation likelihood despite the 7.1 CVSS score.

Technical ContextAI

The vulnerability resides in the accel/ivpu subsystem, which implements the Linux kernel driver for Intel's AI Visual Processing Unit hardware integrated into recent Intel SoCs. Firmware log buffers are processed from Buffer Objects (BOs) - kernel memory allocations mapped to the VPU firmware. The function fw_log_from_bo() was designed to validate header_size and that the log fits within the BO, but omitted the critical check that log->size >= log->header_size. In fw_log_print_buffer(), the expression 'u32 data_size = log->size - log->header_size' performs unsigned 32-bit arithmetic: when log->size < log->header_size, the result wraps to approximately 4,294,967,295 (U32_MAX - delta), completely defeating the log_start/log_end clamp logic added by commit dd1311bcf0e6. This causes fw_log_print_lines() to iterate over a near-maximum-size virtual region, reading kernel memory well past the actual BO allocation. A secondary defect - when log->size == 0, the offset advance is also 0 - causes callers to loop forever on the same malformed header, resulting in a hung kernel thread. While NVD lists CWE as N/A, this maps to CWE-191 (Integer Underflow) leading to CWE-125 (Out-of-Bounds Read) and CWE-835 (Infinite Loop).

RemediationAI

The primary fix is to upgrade to a patched Linux kernel version: 6.6.148, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc4 or later. Upstream fix commits are available on git.kernel.org stable trees (commits 257321a1c036da417f5d9c47b95c7e58f62bf263, 5592a207e158b738d9c1d27f208dbbea13ae7606, 6920e62be4c969a68ce4ebc59da68c6cbc9512e5, dc9a1cda2e46d0254730a6f93cfe48532895f33c, ddb44baed257560f192b145ed36cf8c0a412de47). Distribution maintainers tracking these stable branches (Debian, Ubuntu, RHEL, SUSE, etc.) should apply these upstream patches in their next kernel updates. If an immediate kernel upgrade is not feasible, a targeted compensating control is to blacklist the ivpu kernel module by adding 'blacklist ivpu' to /etc/modprobe.d/ and regenerating the initramfs - this prevents the driver from loading and fully eliminates the attack surface at the cost of losing Intel VPU/AI accelerator functionality. Systems without Intel VPU hardware need no action.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72089 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy