https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 03:15:43 +0000 https://vulnerability.circl.lu/vuln/cve-2026-31585 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: vidtv: fix nfeeds state corruption on start_streaming failure</p> <p>syzbot reported a memory leak in vidtv_psi_service_desc_init [1].</p> <p>When vidtv_start_streaming() fails inside vidtv_start_feed(), the nfeeds counter is left incremented even though no feed was actually started. This corrupts the driver state: subsequent start_feed calls see nfeeds &gt; 1 and skip starting the mux, while stop_feed calls eventually try to stop a non-existent stream.</p> <p>This state corruption can also lead to memory leaks, since the mux and channel resources may be partially allocated during a failed start_streaming but never cleaned up, as the stop path finds dvb-&gt;streaming == false and returns early.</p> <p>Fix by decrementing nfeeds back when start_streaming fails, keeping the counter in sync with the actual number of active feeds.</p> <p>[1] BUG: memory leak unreferenced object 0xffff888145b50820 (size 32): comm &#34;syz.0.17&#34;, pid 6068, jiffies 4294944486 backtrace (crc 90a0c7d4): vidtv_psi_service_desc_init+0x74/0x1b0 drivers/media/test-drivers/vidtv/vidtv_psi.c:288 vidtv_channel_s302m_init+0xb1/0x2a0 drivers/media/test-drivers/vidtv/vidtv_channel.c:83 vidtv_channels_init+0x1b/0x40 drivers/media/test-drivers/vidtv/vidtv_channel.c:524 vidtv_mux_init+0x516/0xbe0 drivers/media/test-drivers/vidtv/vidtv_mux.c:518 vidtv_start_streaming drivers/media/test-drivers/vidtv/vidtv_bridge.c:194 [inline] vidtv_start_feed+0x33e/0x4d0 drivers/m…</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>media: vidtv: fix nfeeds state corruption on start_streaming failure</p> <p>syzbot reported a memory leak in vidtv_psi_service_desc_init [1].</p> <p>When vidtv_start_streaming() fails inside vidtv_start_feed(), the nfeeds counter is left incremented even though no feed was actually started. This corrupts the driver state: subsequent start_feed calls see nfeeds &gt; 1 and skip starting the mux, while stop_feed calls eventually try to stop a non-existent stream.</p> <p>This state corruption can also lead to memory leaks, since the mux and channel resources may be partially allocated during a failed start_streaming but never cleaned up, as the stop path finds dvb-&gt;streaming == false and returns early.</p> <p>Fix by decrementing nfeeds back when start_streaming fails, keeping the counter in sync with the actual number of active feeds.</p> <p>[1] BUG: memory leak unreferenced object 0xffff888145b50820 (size 32): comm &#34;syz.0.17&#34;, pid 6068, jiffies 4294944486 backtrace (crc 90a0c7d4): vidtv_psi_service_desc_init+0x74/0x1b0 drivers/media/test-drivers/vidtv/vidtv_psi.c:288 vidtv_channel_s302m_init+0xb1/0x2a0 drivers/media/test-drivers/vidtv/vidtv_channel.c:83 vidtv_channels_init+0x1b/0x40 drivers/media/test-drivers/vidtv/vidtv_channel.c:524 vidtv_mux_init+0x516/0xbe0 drivers/media/test-drivers/vidtv/vidtv_mux.c:518 vidtv_start_streaming drivers/media/test-drivers/vidtv/vidtv_bridge.c:194 [inline] vidtv_start_feed+0x33e/0x4d0 drivers/m…</p> https://vulnerability.circl.lu/vuln/cve-2026-31585