Buffer Overflow in Linux Kernel AV1 Decoder

Publication date: 2026-05-06

Last updated on: 2026-05-08

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: media: verisilicon: AV1: Fix tile info buffer size Each tile info is composed of: row_sb, col_sb, start_pos and end_pos (4 bytes each). So the total required memory is AV1_MAX_TILES * 16 bytes. Use the correct #define to allocate the buffer and avoid writing tile info in non-allocated memory.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-06

Last Modified

2026-05-08

Generated

2026-07-06

AI Q&A

2026-05-06

EPSS Evaluated

2026-07-05

NVD

CVE-2026-43222

EUVD

EUVD-2026-27782

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.7 (inc) to 6.12.75 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.16 (exc)
linux	linux_kernel	From 6.19 (inc) to 6.19.6 (exc)
linux	linux_kernel	From 6.5 (inc) to 6.6.128 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is related to the Linux kernel's handling of the Verisilicon AV1 media component. Specifically, it involves the incorrect allocation of memory for the tile info buffer. Each tile info consists of four 4-byte fields (row_sb, col_sb, start_pos, and end_pos), requiring a total memory size of AV1_MAX_TILES multiplied by 16 bytes. The vulnerability occurred because the buffer was not allocated using the correct size defined by the appropriate #define, which could lead to writing tile info data into memory that was not properly allocated.

Impact Analysis

The impact of this vulnerability could include memory corruption due to writing beyond the allocated buffer size. This may lead to system instability, crashes, or potentially exploitable conditions depending on how the corrupted memory is used. However, specific impacts such as privilege escalation or data leakage are not detailed in the provided information.

Hi! I’m here to help you understand CVE-2026-43222. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70