Look up another CVE · open CVE-2026-97577 in the interactive tracker
CVE-2026-97577
media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity
Published 2026-09-25 (24 days ago) by the Linux kernel CNA. Subsystem drivers/media. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-97577 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.7-1 | Update the kernel and reboot. Fixed in 7.2.7-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.7-1 | Update the kernel and reboot. Fixed in 7.2.7-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
rockchip_vpu981_av1_dec_set_tile_info() indexes the tile group entry array by tile1 * tile_cols + tile0, reading up to tile_cols * tile_rows entries, lays out one descriptor per tile in the AV1_MAX_TILES tile_info buffer, and programs the real tile_cols / tile_rows into the hardware. The tile group entry control is a dynamic array sized to the number of entries userspace submitted, independent of tile_cols / tile_rows, so a frame that claims more tiles than entries reads past the array. A frame that claims more than AV1_MAX_TILES tiles also leaves the hardware programmed for more tiles than the descriptor buffer holds. Reject both in prepare_run(): tile_cols * tile_rows must not exceed the submitted entry count or AV1_MAX_TILES. The entry count is read via v4l2_ctrl_find() (ctrl->elems). This mirrors the bound the mediatek AV1 decoder already enforces.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/media/platform/verisilicon/rockchip_vpu981_hw_av1_dec.c
- What this is
- HANTRO VPU CODEC DRIVERMAINTAINERS section matched on drivers/media/platform/verisilicon/ · linux-media@vger.kernel.org · Maintained
- Kernel module
- hantro_vpu
Check it on the machine
grep -wE 'CONFIG_VIDEO_HANTRO|CONFIG_VIDEO_HANTRO_ROCKCHIP' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w hantro_vpuPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/cloud-arm64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_VIDEO_HANTRO, CONFIG_VIDEO_HANTRO_ROCKCHIP
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-25 (24 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.16%, higher than 5.2% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/media
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.5 | 6.6.158 | 95ee48eb17c9 |
| 6.5 | 6.12.111 | 40029f7f3539 |
| 6.5 | 6.18.53 | a41babf528f7 |
| 6.5 | 7.2.7 | fd965369220c |
| 6.5 | 7.3 | 367db8b23c26 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The malformed tile_cols/tile_rows and TILE_GROUP_ENTRY data are supplied by a local process through V4L2 request ioctls (VIDIOC_S_EXT_CTRLS + MEDIA_REQUEST_IOC_QUEUE) on the vpu981 /dev/videoN decoder, reaching rockchip_vpu981_av1_dec_run() -> set_tile_info(); no network protocol carries the input.
- AC:LAttack complexity, low
- validate_av1_frame() never bounds tile_cols/tile_rows (u8, up to 255), so setting tile_cols*tile_rows above 128 makes set_tile_info() deterministically write 16 bytes per tile past the 2KB AV1_TILE_INFO_SIZE buffer, with no race and no outside condition.
- PR:LPrivileges required, low
- No capability check guards the stateless decoder's controls or request queue; the attacker only needs open access to the /dev/videoN node, which desktop udev grants to the logged-in seat user (uaccess) or the video group, i.e. an ordinary local user.
- UI:NUser interaction, none
- The attacker builds the AV1 frame and tile group entry controls and queues the decode request themselves; no other user has to act.
- S:UScope, unchanged
- The corruption is of kernel memory adjacent to the tile_info coherent buffer, and the resulting impact stays within the kernel's own authority; no VM, IOMMU or sandbox boundary is crossed.
- C:HConfidentiality impact, high
- set_tile_info() reads group_entry[tile_id] past the dynamic TILE_GROUP_ENTRY array and width/height_in_sbs_minus_1[] past 64 entries; this out-of-bounds heap read is not strictly bounded to a few bytes, and the write primitive enables further disclosure.
- I:HIntegrity impact, high
- The loop writes tile_cols*tile_rows*16 bytes (up to ~1MB) into a 2KB dma_alloc_coherent buffer, with attacker-controlled tile_offset/tile_size and tile width/height bytes, giving an out-of-bounds kernel memory write of attacker-controlled data and length.
- A:HAvailability impact, high
- A large overflow past the tile_info allocation corrupts adjacent kernel memory or faults on an unmapped guard page, causing a kernel oops or panic that the attacker can repeat at will.