CVE-2026-31583

HIGHCVSS · not yet scored7.8
EchelonGraph scoreLOW confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation 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: em28xx: fix use-after-free in em28xx_v4l2_open()

em28xx_v4l2_open() reads dev->v4l2 without holding dev->lock, creating a race with em28xx_v4l2_init()'s error path and em28xx_v4l2_fini(), both of which free the em28xx_v4l2 struct and set dev->v4l2 to NULL under dev->lock.

This race leads to two issues:

  • use-after-free in v4l2_fh_init() when accessing vdev->ctrl_handler,
since the video_device is embedded in the freed em28xx_v4l2 struct.
  • NULL pointer dereference in em28xx_resolution_set() when accessing
v4l2->norm, since dev->v4l2 has been set to NULL.

Fix this by moving the mutex_lock() before the dev->v4l2 read and adding a NULL check for dev->v4l2 under the lock.

CVSS v3
—
EG Score
7.8(low)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 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

Advisory Details (9)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd2b888e08d3b3d6aacd65d76cd44fac11da750f
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b5d141ea15f173f15b9f0a72965902f3428c0d92
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a66485a934c7187ae8e36517d40615fa2e961cff
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/871b8ea8ef39a6c253594649f4339378fad3d0dd
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b9e66437cc6123ddedac141e1b8b6fcf57d2972
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fb2940327722b4684d2f964b54c1c90aa277324
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c0283a59e36e3707c4a81f4952e362d31f876b8
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38a327221f7f765e7d853b7bafe47e342441ec85
generic

media: em28xx: fix use-after-free in em28xx_v4l2_open() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2cbf81f76842e46bdf25823c70e1db4044a65678

Vendor Advisories for CVE-2026-31583(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 (126 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 5× in last 7d / 73× 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 260 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-31583?
CVE-2026-31583 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: media: em28xx: fix use-after-free in em28xxv4l2open() em28xxv4l2open() reads dev->v4l2 without holding dev->lock, creating a race with em28xxv4l2init()'s error path and em28xxv4l2fini(), both of which free the em28xx_v4l2 struct…
When was CVE-2026-31583 disclosed?
CVE-2026-31583 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-31583 actively exploited?
CVE-2026-31583 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.3% of all scored CVEs.
How do I remediate CVE-2026-31583?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31583, 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-31583

Explore →

Is Your Infrastructure Affected by CVE-2026-31583?

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

Start Free Scan →Browse All CVEs