Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-31585 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

media: vidtv: fix nfeeds state corruption on start_streaming failure

In the Linux kernel, the following vulnerability has been resolved:

media: vidtv: fix nfeeds state corruption on start_streaming failure

syzbot reported a memory leak in vidtv_psi_service_desc_init [1].

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 > 1 and skip starting the mux, while stop_feed calls

eventually try to stop a non-existent stream.

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->streaming == false and returns early.

Fix by decrementing nfeeds back when start_streaming fails, keeping

the counter in sync with the actual number of active feeds.

[1]

BUG: memory leak

unreferenced object 0xffff888145b50820 (size 32):

comm "syz.0.17", 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/media/test-drivers/vidtv/vidtv_bridge.c:239

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2026-31585 is recorded against 2 packages.

  • kernel (from 6.20.0 up to 7.0.1)
  • linux-kernel (from 7.0 up to 7.0.1)

Timeline and source

Published on 24 April 2026 and last revised on 15 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2026-31585 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-04-24
Updated 2026-08-20
Modified 2026-08-15

Affected Packages

Software From version Fixed in
kernel 6.20.0 7.0.1
linux-kernel 7.0 7.0.1

References

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2026-31585 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.