CVE-2026-31585

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-04-24.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
—
EG Score
5.5(low)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

References (9)

Vendor Advisories for CVE-2026-31585(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 224 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-17 19:30 UTCEPSS rescore
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-04 03:16 UTCOSV refresh
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:17 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 14:52 UTCEG score recompute
  11. 2026-08-17 14:52 UTCVendor advisory
  12. 2026-08-17 14:52 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 05:48 UTCEG score recompute
  16. 2026-08-16 05:48 UTCVendor advisory
  17. 2026-08-16 05:48 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 04:08 UTCEG score recompute
  21. 2026-08-14 04:08 UTCVendor advisory
  22. 2026-08-14 04:08 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 17:51 UTCEG score recompute
  25. 2026-08-12 17:51 UTCVendor advisory
  26. 2026-08-12 17:51 UTCGHSA enrichment
  27. 2026-08-12 13:50 UTCEPSS rescore
  28. 2026-08-11 16:41 UTCEG score recompute
  29. 2026-08-11 16:41 UTCVendor advisory
  30. 2026-08-11 16:41 UTCGHSA enrichment
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 12:10 UTCEG score recompute
  33. 2026-08-10 12:10 UTCVendor advisory
  34. 2026-08-10 12:10 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 12:38 UTCEG score recompute
  37. 2026-08-09 12:38 UTCVendor advisory
  38. 2026-08-09 12:38 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 12:16 UTCVendor advisory
  41. 2026-08-08 12:16 UTCGHSA enrichment
  42. 2026-08-07 12:36 UTCEG score recompute
  43. 2026-08-07 12:36 UTCVendor advisory
  44. 2026-08-07 12:36 UTCGHSA enrichment
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-05 22:57 UTCEG score recompute
  47. 2026-08-05 22:57 UTCVendor advisory
  48. 2026-08-05 22:57 UTCGHSA enrichment
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:38 UTCEPSS rescore
  52. 2026-08-03 21:03 UTCVendor advisory
  53. 2026-08-03 21:03 UTCGHSA enrichment
  54. 2026-08-02 11:22 UTCEG score recompute
  55. 2026-08-02 11:22 UTCVendor advisory
  56. 2026-08-02 11:22 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 04:16 UTCEPSS rescore
  59. 2026-07-30 16:27 UTCEPSS rescore
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-28 15:36 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 14:54 UTCEPSS rescore
  64. 2026-07-24 14:17 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 03:08 UTCEG score recompute
  68. 2026-07-22 14:08 UTCEPSS rescore
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:24 UTCEPSS rescore
  71. 2026-07-21 15:24 UTCEPSS rescore
  72. 2026-07-20 17:08 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 23:08 UTCOSV refresh
  75. 2026-07-19 14:31 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-31585?
CVE-2026-31585 is a medium vulnerability published on April 24, 2026. 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 vidtvpsiservicedescinit [1]. When vidtvstartstreaming() fails inside vidtvstartfeed(), the nfeeds counter is left incremented…
When was CVE-2026-31585 disclosed?
CVE-2026-31585 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31585 actively exploited?
CVE-2026-31585 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
How do I remediate CVE-2026-31585?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31585, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31585

Explore →

Is Your Infrastructure Affected by CVE-2026-31585?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs