LiveActive security incident?Get immediate response
CVE Record

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

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

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux’s Amphion video-processing driver can use memory after it is freed, causing a kernel panic. This can disrupt the entire host. The supplied evidence demonstrates a crash; it does not demonstrate data theft, system takeover, or remote exploitation.

Executive priority

Treat this as a high-priority stability and local-security update for confirmed Amphion deployments, especially shared or multi-user systems. It does not warrant an internet-wide emergency response based on current evidence, but exposed hosts should enter the next expedited kernel maintenance cycle.

Technical view

A timing race between v4l2_m2m_try_run() and v4l2_m2m_ctx_release() allows device_run() to receive a freed m2m context. The Linux fix prevents m2m framework job scheduling through job_ready and removes job_abort, which participated in the unsafe release sequence.

Likely exposure

Exposure requires an affected Linux kernel, the Amphion VPU driver, and a reachable local path to the relevant media functionality. The bundle identifies affected versions from 5.18 across several stable branches through 7.1, but does not clearly provide branch-specific version ranges.

Exploitation context

KEV is false, and no supplied source reports active exploitation or a public exploit. CVSS indicates local access, low privileges, low complexity, and no user interaction. The documented result is a kernel panic; broader compromise is reflected in scoring but not demonstrated by the evidence.

Researcher notes

The root cause is unsafe context lifetime synchronization across job execution and cancellation. The fix is driver-specific because Amphion does not depend on the m2m framework’s device_run callback for encoding or decoding. Evidence confirms a use-after-free crash, not reliable privilege escalation or code execution.

Mitigation direction

  • Identify systems using the Amphion VPU driver and compare their kernels with vendor advisories.
  • Upgrade to a vendor kernel containing the applicable referenced Linux stable fix.
  • If unavailable, request vendor-supported mitigation; the supplied sources identify no safe configuration workaround.
  • Prioritize shared systems and hosts permitting untrusted local users.

Validation and detection

  • Confirm the running kernel includes the applicable stable commit or vendor backport.
  • Verify whether the Amphion VPU driver is present and active on candidate systems.
  • Check vendor release notes for precise affected and fixed boundaries on each kernel branch.
  • Review kernel logs for panics referencing v4l2_m2m_try_run or the documented unreadable address.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46058 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-46058Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3cd084519c6f91cbef9d604bcf26844fa81d4922, 3cd084519c6f91cbef9d604bcf26844fa81d4922, 3cd084519c6f91cbef9d604bcf26844fa81d4922, 3cd084519c6f91cbef9d604bcf26844fa81d4922, 3cd084519c6f91cbef9d604bcf26844fa81d4922, 3cd084519c6f91cbef9d604bcf26844fa81d4922unaffected
LinuxLinux5.18, 0, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.