CVE-2026-53382

CVE CVE-2026-53382EUVD EUVD-2026-45504Published 2026-07-19T11:59:31.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: media: vidtv: fix NULL pointer dereference in vidtv_mux_push_si syzbot reported a general protection fault in vidtv_psi_ts_psi_write_into [1]. vidtv_mux_get_pid_ctx() can return NULL, but vidtv_mux_push_si() does not check for this before dereferencing the returned pointer to access the continuity counter. This leads to a general protection fault when accessing a near-NULL address. The root cause is that vidtv_mux_pid_ctx_init() does not check the return value of vidtv_mux_create_pid_ctx_once() for PMT section PIDs. If the allocation fails, the PID context is never created, but init returns success. The subsequent vidtv_mux_push_si() call then gets NULL from vidtv_mux_get_pid_ctx() and crashes. Fix both the root cause (add error check in vidtv_mux_pid_ctx_init for PMT PIDs) and add defensive NULL checks in vidtv_mux_push_si for all vidtv_mux_get_pid_ctx() calls. [1] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: events vidtv_mux_tick RIP: 0010:vidtv_psi_ts_psi_write_into+0x54a/0xbc0 drivers/media/test-drivers/vidtv/vidtv_psi.c:197 Call Trace: <TASK> vidtv_psi_table_header_write_into drivers/media/test-drivers/vidtv/vidtv_psi.c:799 [inline] vidtv_psi_pmt_write_into+0x3b2/0xa70 drivers/media/test-drivers/vidtv/vidtv_psi.c:1231 vidtv_mux_push_si+0x932/0xe80 drivers/media/test-drivers/vidtv/vidtv_mux.c:196 vidtv_mux_tick+0xe9b/0x1480 drivers/media/test-drivers/vidtv/vidtv_mux.c:408

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux f90cf6079bf67988f8b1ad1ade70fc89d0080905 <232e4b313ea342672edf8947e067c0de4328405b; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <353d9578951dd38bc9679308f5b618ceed1f20fa; 5.10; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <455bc12e7b73ab5a2dfcb47822e91e772bc6c42e; patch: 6.18.37; patch: 0; patch: 5.15.211; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <b28b12be6e8910489e6800ed93ea4d41dfe19683; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <cd923dadefadb9671b5ac341b672ff424d429c39; patch: 6.12.95; patch: 7.1.2; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <f965cf22dda7f512f4922415894c3e528269a4ae; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <7d8bf3d8f91073f4db347ed3aa6302b56107499c; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <f0f5a1d7056980a0d512456fdb370cfb72bba86a; patch: 7.0.14; patch: 5.10.260; patch: 6.6.144; f90cf6079bf67988f8b1ad1ade70fc89d0080905 <6df7e16d4f742c80add58995a6e69385b97aa9e6; patch: 6.1.177; patch: 7.2-rc1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.