Look up another CVE · open CVE-2026-97578 in the interactive tracker
CVE-2026-97578
media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer
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-97578 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() divides context_update_tile_id by tile_info->tile_cols and writes one descriptor per tile into the tile_info DMA buffer, which holds AV1_MAX_TILES entries; tile_cols and tile_rows come from the bitstream. Guard the division against a zero tile_cols by initialising the context-update values to zero and computing them only when tile_cols is non-zero, and stop the descriptor writes once the tile_info buffer is full. The tile geometry written to the hardware registers is left unmodified; the per-dimension and total tile bounds are enforced by the control validation.
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 | 8659e5fc21a8 |
| 6.5 | 6.12.111 | 7baa7bb1b784 |
| 6.5 | 6.18.53 | 8f19d869a9f6 |
| 6.5 | 7.2.7 | 6b7a281a815a |
| 6.5 | 7.3 | b84f6533a8ed |
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 bad tile_cols/tile_rows reach rockchip_vpu981_av1_dec_set_tile_info() through the V4L2_CID_STATELESS_AV1_FRAME control, set with VIDIOC_S_EXT_CTRLS/media request ioctls on the local hantro /dev/videoN node and run via rockchip_vpu981_av1_dec_run(). No remote protocol carries the values; a userspace AV1 parser would have to pass through values that break the spec.
- AC:LAttack complexity, low
- validate_av1_frame() never checks tile_cols or tile_rows, so any caller can set tile_cols=0 (divide by zero) or 255x255 tiles (writes far past the 2 KiB tile_info buffer). Nothing outside the attacker's control is needed; the fault happens every time the job runs.
- PR:LPrivileges required, low
- The only requirement is opening the VPU981 AV1 stateless decoder video node, which the logged-in user (video group) or the Android/ChromeOS media codec process normally can do. The ioctl path has no capability check.
- UI:NUser interaction, none
- The attacker queues the malicious control and request themselves, and the device_run worker processes it without any action by another user.
- S:UScope, unchanged
- The corruption stays in the kernel's own memory and security authority. No VM, IOMMU, or other boundary is crossed.
- C:HConfidentiality impact, high
- tile_id reaches about 65,000 while the tile_group_entry dynamic array holds at most 512 entries, and indexes of width/height_in_sbs_minus_1 above 64 run past those arrays. Out-of-bounds kernel data is read into the descriptors, and the memory corruption can be used to leak data.
- I:HIntegrity impact, high
- The loop writes 16 bytes per tile, up to 255*255 tiles (about 1 MiB), past the 128-entry (2 KiB) dma_alloc_coherent tile_info buffer. The x0/y0/start/end values it writes are largely user-controlled, so it is a large, content-controlled kernel memory overwrite.
- A:HAvailability impact, high
- tile_cols=0 causes a divide error when computing context_update_tile_id, which oopses the kernel. The large out-of-bounds write also corrupts memory next to the buffer and crashes the system.