{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99214 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99214 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99214 and fix it if it is affected.\n\nWhat it is: CVE-2026-99214 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99214 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99214/ (Markdown: https://insights.sbomify.com/CVE-2026-99214/index.md)","id":"CVE-2026-99214","markdown":"https://insights.sbomify.com/CVE-2026-99214/index.md","name":"CVE-2026-99214","record":{"aliases":["BELL-CVE-2026-99214","DEBIAN-CVE-2026-99214","GHSA-83m6-cmv8-x4pq","UBUNTU-CVE-2026-99214"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: hdmi: Move packet RAM enable to PM runtime\n\nAudio can be triggered by the HPD handler and start up before video has\nbeen restored, calling vc4_hdmi_write_infoframe() for the audio infoframe.\nvc4_hdmi_write_infoframe() needs Packet RAM to be on to store the\ninfoframe, however, if the video hasn't been enabled,\nvc4_hdmi_encoder_post_crtc_enable() hasn't been called and therefore, the\nPacket RAM can be disabled by the time vc4_hdmi_write_infoframe() executes,\ncausing the following splat:\n\n[  201.570266] ------------[ cut here ]------------\n[  201.570293] Packet RAM has to be on to store the packet.\n[  201.570367] WARNING: drivers/gpu/drm/vc4/vc4_hdmi.c:683 at vc4_hdmi_write_infoframe+0x404/0x494 [vc4], CPU#0: wireplumber/1606\n[...]\n[  201.658650] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT)\n[...]\n[  201.758499] Call trace:\n[  201.760967]  vc4_hdmi_write_infoframe+0x404/0x494 [vc4] (P)\n[  201.766607]  vc4_hdmi_write_audio_infoframe+0x1c/0x28 [vc4]\n[  201.772247]  write_infoframe+0xbc/0x140 [drm_display_helper]\n[  201.777975]  drm_atomic_helper_connector_hdmi_update_audio_infoframe+0x80/0xdc [drm_display_helper]\n[  201.787140]  vc4_hdmi_audio_prepare+0x4ac/0x570 [vc4]\n[  201.792252]  drm_connector_hdmi_audio_prepare+0x24/0x30 [drm_display_helper]\n[  201.799390]  hdmi_codec_prepare+0x100/0x160 [snd_soc_hdmi_codec]\n[  201.805471]  snd_soc_pcm_dai_prepare+0xd4/0x100 [snd_soc_core]\n[  201.811375]  __soc_pcm_prepare+0x60/0x12c [snd_soc_core]\n[  201.816752]  soc_pcm_prepare+0x34/0x58 [snd_soc_core]\n[  201.821863]  snd_pcm_do_prepare+0x70/0x8c [snd_pcm]\n[  201.826798]  snd_pcm_action_nonatomic+0xe4/0x174 [snd_pcm]\n[  201.832350]  snd_pcm_prepare+0xc8/0xd8 [snd_pcm]\n[  201.837021]  snd_pcm_common_ioctl+0x458/0x614 [snd_pcm]\n[  201.842308]  snd_pcm_ioctl+0x30/0x48 [snd_pcm]\n[  201.846802]  __arm64_sys_ioctl+0x88/0xd8\n[  201.850769]  invoke_syscall+0x48/0xf4\n[  201.854470]  el0_svc_common+0x80/0xd8\n[  201.858171]  do_el0_svc+0x1c/0x28\n[  201.861520]  el0_svc+0x3c/0xb0\n[  201.864605]  el0t_64_sync_handler+0x68/0xdc\n[  201.868834]  el0t_64_sync+0x198/0x19c\n[  201.872536] ---[ end trace 0000000000000000 ]---\n\nConsidering that Packet RAM enable is essentially a power management\nconfiguration, move its enabling/disabling to the Runtime PM hooks.\n\nNote that post_crtc_disable() still stops all infoframes, but keeps Packet\nRAM enabled, leaving it to be disabled by runtime suspend.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/vc4: hdmi: Move packet RAM enable to PM runtime","id":"CVE-2026-99214","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"power: supply: core: prevent unregistering a power supply while a callback runs","id":"CVE-2026-99215"},"packages":[],"prev":{"headline":"vsock: treat TCP_CLOSING as once-established","id":"CVE-2026-99213"},"products":["Linux"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99214/"}