CVE-2026-46058

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, 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: 7.8Exploit: None knownExposed: 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 PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 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(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
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.86-1~bpo12+1 (19 versions)6.12.86-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

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 3× in last 7d / 82× 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 259 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 5, 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% probability of exploitation in the next 30 days, which ranks it in the top 99.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46058?
CVE-2026-46058 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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