CVE-2026-43222: media: verisilicon: AV1: Fix tile info buffer size
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.
Security readout for executives and security teams
Plain-English summary
A Linux kernel AV1 video-decoding driver allocates too little memory for tile information, allowing data to be written outside the allocated buffer. A successful local attack could compromise confidentiality, integrity, and availability. Exposure appears limited to systems using the affected Verisilicon AV1 media path.
Executive priority
Treat as a high-priority kernel update for systems using Verisilicon AV1 decoding, especially shared or locally accessible platforms. Broad emergency action is not supported by the evidence because exploitation requires local access and no active exploitation is documented. Establish exposure quickly, then patch affected systems through normal expedited maintenance.
Technical view
The Verisilicon AV1 driver requires 16 bytes per tile for row, column, start, and end fields. The vulnerable allocation uses an undersized buffer, causing an out-of-bounds kernel-memory write when tile information is populated. The supplied CVSS 3.1 score is 7.8, requiring local access and low privileges without user interaction.
Likely exposure
Potentially exposed systems run an affected Linux kernel and provide access to the Verisilicon AV1 decoding functionality. The source identifies versions 6.5, 6.6.128, 6.12.75, 6.18.16, 6.19.6, and 7.0 as affected, but its version formatting is ambiguous; verify distribution-specific status.
Exploitation context
The supplied CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. Successful exploitation may affect confidentiality, integrity, and availability. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The correction allocates AV1_MAX_TILES multiplied by 16 bytes, matching four four-byte fields per tile. The bundle supplies five stable-kernel fix commits and repeatedly identifies commit 727a400686a2 as affected. Exact vulnerable ranges and branch mappings are not clearly represented, so validate ancestry or rely on distribution advisories.
Mitigation direction
Apply the appropriate vendor or distribution kernel update containing the referenced fix.
Prioritize systems exposing Verisilicon AV1 decoding to untrusted or low-privileged users.
If updates are unavailable, consult vendor guidance about safely disabling or restricting the affected media functionality.
Restrict local access and untrusted media-processing workloads until remediation is confirmed.
Validation and detection
Record the running kernel version and distribution package release on potentially exposed systems.
Confirm whether the kernel includes the Verisilicon AV1 driver and affected decoding path.
Compare kernel packages against distribution advisories and the referenced stable commits.
After updating, reboot and verify the running kernel contains the applicable fix.
Review system telemetry for kernel crashes or memory-corruption events involving Verisilicon AV1 processing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43222 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.