CVE-2026-46058

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

media: amphion: Fix race between m2m job_abort and device_run

Fix kernel panic caused by race condition where v4l2_m2m_ctx_release() frees m2m_ctx while v4l2_m2m_try_run() is about to call device_run with the same context.

Race sequence: v4l2_m2m_try_run(): v4l2_m2m_ctx_release(): lock/unlock v4l2_m2m_cancel_job() job_abort() v4l2_m2m_job_finish() kfree(m2m_ctx) <- frees ctx device_run() <- use-after-free crash at 0x538

Crash trace: Unable to handle kernel read from unreadable memory at virtual address 0000000000000538 v4l2_m2m_try_run+0x78/0x138 v4l2_m2m_device_run_work+0x14/0x20

The amphion vpu driver does not rely on the m2m framework's device_run callback to perform encode/decode operations.

Fix the race by preventing m2m framework job scheduling entirely:

  • Add job_ready callback returning 0 (no jobs ready for m2m framework)
  • Remove job_abort callback to avoid the race condition

CVSS v3
7.8
EG Score
7.8(medium)
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
0.9%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (6)

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

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8cd35ceadcfc8c5da2eb7f7ce24525ce9d4ee62e
generic

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/516467052fdfc6a13eadc70d43420ae57436bf3c
generic

media: amphion: Fix race between m2m job_abort and device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42dc622776f3ce1a6c31b13bdc686f7295e3b323

Vendor Advisories for CVE-2026-46058(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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 6× in last 7d / 44× 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 140 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46058?
CVE-2026-46058 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: media: amphion: Fix race between m2m jobabort and devicerun Fix kernel panic caused by race condition where v4l2m2mctx_release() frees m2mctx while v4l2m2mtryrun() is about to call device_run with the same context. Race sequence:…
When was CVE-2026-46058 disclosed?
CVE-2026-46058 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46058 actively exploited?
CVE-2026-46058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46058?
CVE-2026-46058 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46058?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46058, 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

Explore the affected products and dependency analysis for CVE-2026-46058

Explore →

Is Your Infrastructure Affected by CVE-2026-46058?

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

Start Free Scan →Browse All CVEs