Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-46058media: amphion: Fix race between m2m job_abort and device_run

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46058, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < 516467052fdfc6a13eadc70d43420ae57436bf3c
    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < 42dc622776f3ce1a6c31b13bdc686f7295e3b323
    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < da4f46c5cf1d26e6b09418ad453e152f2e75a02c
    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < fdc150dac1adb9a98be9d6956cff0348838b024a
    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < 6be2cb75bc1300080cfc8051579f22efae9401f7
    • affected 3cd084519c6f91cbef9d604bcf26844fa81d4922 – < 8cd35ceadcfc8c5da2eb7f7ce24525ce9d4ee62e
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46058 badge
[![CVE-2026-46058](https://cveledger.app/badge/CVE-2026-46058.svg)](https://cveledger.app/cve/CVE-2026-46058)

Record last updated .