# CVE-2026-99214: linux: In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: hdmi: Move packet RAM enable to PM runt...

CVE-2026-99214 is fixed in linux on 1 platform, first by DEBIAN-CVE-2026-99214, released November 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-99214
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0016
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 28, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: hdmi: Move packet RAM enable to PM runtime  Audio can be triggered by the HPD handler and start up before video has been restored, calling vc4_hdmi_write_infoframe() for the audio infoframe. vc4_hdmi_write_infoframe() needs Packet RAM to be on to store the infoframe, however, if the video hasn't been enabled, vc4_hdmi_encoder_post_crtc_enable() hasn't been called and therefore, the Packet RAM can be disabled by the time vc4_hdmi_write_infoframe() executes, causing the following splat:  [  201.570266] ------------[ cut here ]------------ [  201.570293] Packet RAM has to be on to store the packet. [  201.570367] WARNING: drivers/gpu/drm/vc4/vc4_hdmi.c:683 at vc4_hdmi_write_infoframe+0x404/0x494 [vc4], CPU#0: wireplumber/1606 [...] [  201.658650] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT) [...] [  201.758499] Call trace: [  201.760967]  vc4_hdmi_write_infoframe+0x404/0x494 [vc4] (P) [  201.766607]  vc4_hdmi_write_audio_infoframe+0x1c/0x28 [vc4] [  201.772247]  write_infoframe+0xbc/0x140 [drm_display_helper] [  201.777975]  drm_atomic_helper_connector_hdmi_update_audio_infoframe+0x80/0xdc [drm_display_helper] [  201.787140]  vc4_hdmi_audio_prepare+0x4ac/0x570 [vc4] [  201.792252]  drm_connector_hdmi_audio_prepare+0x24/0x30 [drm_display_helper] [  201.799390]  hdmi_codec_prepare+0x100/0x160 [snd_soc_hdmi_codec] [  201.805471]  snd_soc_pcm_dai_prepare+0xd4/0x100 [snd_soc_core] [  201.811375]  __soc_pcm_prepare+0x60/0x12c [snd_soc_core] [  201.816752]  soc_pcm_prepare+0x34/0x58 [snd_soc_core] [  201.821863]  snd_pcm_do_prepare+0x70/0x8c [snd_pcm] [  201.826798]  snd_pcm_action_nonatomic+0xe4/0x174 [snd_pcm] [  201.832350]  snd_pcm_prepare+0xc8/0xd8 [snd_pcm] [  201.837021]  snd_pcm_common_ioctl+0x458/0x614 [snd_pcm] [  201.842308]  snd_pcm_ioctl+0x30/0x48 [snd_pcm] [  201.846802]  __arm64_sys_ioctl+0x88/0xd8 [  201.850769]  invoke_syscall+0x48/0xf4 [  201.854470]  el0_svc_common+0x80/0xd8 [  201.858171]  do_el0_svc+0x1c/0x28 [  201.861520]  el0_svc+0x3c/0xb0 [  201.864605]  el0t_64_sync_handler+0x68/0xdc [  201.868834]  el0t_64_sync+0x198/0x19c [  201.872536] ---[ end trace 0000000000000000 ]---  Considering that Packet RAM enable is essentially a power management configuration, move its enabling/disabling to the Runtime PM hooks.  Note that post_crtc_disable() still stops all infoframes, but keeps Packet RAM enabled, leaving it to be disabled by runtime suspend.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2026-99214](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99214.md) | Nov 3, 2026 |
| Linux | linux Debian 14 | 7.2.13-1 | [DEBIAN-CVE-2026-99214](https://patchblox.com/security/data/fix/linux/debian-cve-2026-99214.md) | Nov 3, 2026 |

---

Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.