CVE-2026-53202: accel/ivpu: Fix signed integer truncation in IPC receive

Published Jun 25, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

accel/ivpu: Fix signed integer truncation in IPC receive

Fix potential buffer overflow where firmware-supplied datasize is cast to signed int before being used in mint(). Large unsigned values (>= 0x80000000) become negative, causing unsigned wraparound and oversized memcpy operations that can overflow the stack buffer.

Change mint(int, ...) to min() as both values are unsigned and can be handled by min() without explicit cast.

Affected Software

11 affected components
Linux Linux kernel
Linux Linux kernel>=6.8<6.12.94
Linux Linux kernel>=6.13<6.18.36
Linux Linux kernel>=6.19<7.0.13
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6
Linux Linux kernel=7.1-rc7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the accel/ivpu code so min_t(int, ...) is changed to min() since both values are unsigned and can become negative (>= 0x80000000) causing unsigned wraparound; and handle oversized memcpy operations by avoiding casts to signed int before being used in min_t().

    Linux kernel (accel/ivpu) min_t(int, ...) replaced with min() = Use min() for unsigned values instead of min_t(int, ...) to avoid signed integer truncation
  2. Configuration

    Fix the potential buffer overflow by preventing firmware-supplied data_size from being cast to a signed int before being used (so oversized memcpy operations cannot overflow the stack buffer).

    Linux kernel (accel/ivpu) firmware-supplied data_size casting = Avoid casting firmware-supplied data_size to a smaller signed int before it is used to compute/cap memcpy length

Event History

Jun 25, 2026
CVE Published
via MITRE·08:39 AM
Data Sourced
via MITRE·08:39 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·10:07 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What level of access and control does an attacker need?

Exploitation requires local access and low privileges, according to the CVSS vector. The vulnerable input is firmware-supplied IPC data_size, so an attacker would need a way to cause the driver to process a maliciously large firmware-provided value.

2

How can I determine whether my kernel contains the vulnerable code?

Affected systems can be identified by reviewing the accel/ivpu IPC receive implementation for data_size being cast to signed int and passed to min_t(int, ...). The corrected code uses min() with unsigned values, preventing values at or above 0x80000000 from becoming negative.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203