BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-46058High confidence

media: amphion: Fix race between m2m job_abort and device_run

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.86-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-46058 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-46058
47 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-devel as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-macros as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP6-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
  • dlm-kmp-default as component of SUSE Linux Enterprise Server 15 SP6
Summary
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
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-32440

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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

What

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

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

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

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-362
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46044 Référence CVE CVE-2026-46046 https://www.cve.org/CVERecord?id=CVE-2026-46046 Référence CVE CVE-2026-46047 https://www.cve.org/CVERecord?id=CVE-2026-46047 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46061 https://www.cve.org/CVERecord?id=CVE-2026-46061 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46068 https://www.cve.org/CVERecord?id=CVE-2026-46068 Référence CVE CVE-2026-46069 https://www.cve.org/CVERecord?id=CVE-2026-46069 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46027 Référence CVE CVE-2026-46033 https://www.cve.org/CVERecord?id=CVE-2026-46033 Référence CVE CVE-2026-46034 https://www.cve.org/CVERecord?id=CVE-2026-46034 Référence CVE CVE-2026-46036 https://www.cve.org/CVERecord?id=CVE-2026-46036 Référence CVE CVE-2026-46038 https://www.cve.org/CVERecord?id=CVE-2026-46038 Référence CVE CVE-2026-46040 https://www.cve.org/CVERecord?id=CVE-2026-46040 Référence CVE CVE-2026-46048 https://www.cve.org/CVERecord?id=CVE-2026-46048 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46060 https://www.cve.org/CVERecord?id=CVE-2026-46060 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46068 https://www.cve.org/CVERecord?id=CVE-2026-46068 Référence CVE CVE-2026-46073 https://www.cve.org/CVERecord?id=CVE-2026-46073 Référence CVE CVE-2026-46074 https://www.cve.org/CVERecord?id=CVE-2026-46074 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=CVE-2026-46075 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46047 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46057 https://www.cve.org/CVERecord?id=CVE-2026-46057 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46060 https://www.cve.org/CVERecord?id=CVE-2026-46060 Référence CVE CVE-2026-46061 https://www.cve.org/CVERecord?id=CVE-2026-46061 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46066 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-46040 Référence CVE CVE-2026-46046 https://www.cve.org/CVERecord?id=CVE-2026-46046 Référence CVE CVE-2026-46048 https://www.cve.org/CVERecord?id=CVE-2026-46048 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46068 https://www.cve.org/CVERecord?id=CVE-2026-46068 Référence CVE CVE-2026-46069 https://www.cve.org/CVERecord?id=CVE-2026-46069 Référence CVE CVE-2026-46071 https://www.cve.org/CVERecord?id=CVE-2026-46071 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46047 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46057 https://www.cve.org/CVERecord?id=CVE-2026-46057 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46060 https://www.cve.org/CVERecord?id=CVE-2026-46060 Référence CVE CVE-2026-46061 https://www.cve.org/CVERecord?id=CVE-2026-46061 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46066 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-46046 Référence CVE CVE-2026-46047 https://www.cve.org/CVERecord?id=CVE-2026-46047 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46069 https://www.cve.org/CVERecord?id=CVE-2026-46069 Référence CVE CVE-2026-46070 https://www.cve.org/CVERecord?id=CVE-2026-46070 Référence CVE CVE-2026-46072 https://www.cve.org/CVERecord?id=CVE-2026-46072 Référence CVE CVE-2026-46075 https://www.cve.org/CVERecord?id=CVE-2026-46075 Référence CVE CVE-2026-46077 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0861Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46047 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46057 https://www.cve.org/CVERecord?id=CVE-2026-46057 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46060 https://www.cve.org/CVERecord?id=CVE-2026-46060 Référence CVE CVE-2026-46061 https://www.cve.org/CVERecord?id=CVE-2026-46061 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46066 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0831Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46048 Référence CVE CVE-2026-46049 https://www.cve.org/CVERecord?id=CVE-2026-46049 Référence CVE CVE-2026-46050 https://www.cve.org/CVERecord?id=CVE-2026-46050 Référence CVE CVE-2026-46051 https://www.cve.org/CVERecord?id=CVE-2026-46051 Référence CVE CVE-2026-46052 https://www.cve.org/CVERecord?id=CVE-2026-46052 Référence CVE CVE-2026-46053 https://www.cve.org/CVERecord?id=CVE-2026-46053 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46057 https://www.cve.org/CVERecord?id=CVE-2026-46057 Référence CVE CVE-2026-46058 https://www.cve.org/CVERecord?id=CVE-2026-46058 Référence CVE CVE-2026-46059 https://www.cve.org/CVERecord?id=CVE-2026-46059 Référence CVE CVE-2026-46060 https://www.cve.org/CVERecord?id=CVE-2026-46060 Référence CVE CVE-2026-46061 https://www.cve.org/CVERecord?id=CVE-2026-46061 Référence CVE CVE-2026-46062 https://www.cve.org/CVERecord?id=CVE-2026-46062 Référence CVE CVE-2026-46063 https://www.cve.org/CVERecord?id=CVE-2026-46063 Référence CVE CVE-2026-46064 https://www.cve.org/CVERecord?id=CVE-2026-46064 Référence CVE CVE-2026-46065 https://www.cve.org/CVERecord?id=CVE-2026-46065 Référence CVE CVE-2026-46066 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0731Multiples vulnérabilités dans les produits Microsoft

mai 2026 Bulletin de sécurité Microsoft CVE-2026-46043 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46046 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46047 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46048 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46049 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46050 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46051 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46052 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46053 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46056 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46058 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46062 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46063 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46064 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46065 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46068 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46069 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46070 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46072 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46075 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46077 du 28 mai 2026 Bulletin de sécurité Mic

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-020032LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、media: amphionのm2mジョブの中止とdevice_run呼び出しの間で発生する競合状態の脆弱性が修正されました。この競合状態により、v4l2_m2m_ctx_release()がm2mコンテキストを解放した後に、v4l2_m2m_try_run()が解放済みのコンテキストにアクセスし、use-after-freeによるカーネルパニックが発生していました。本脆弱性はamphion vpuドライバがm2mフレームワークのdevice_runコールバックを使用していなかったことに起因しており、競合状態を防止するためにjob_readyコールバックを追加してジョブスケジューリングを制限し、job_abortコールバックを削除することで修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.18, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.86 ≤ 6.12.*, 6.18.27 ≤ 6.18.*, 7.0.4 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 May 2026 · Last source change 5 Aug 2026, 12:29 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-32440
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-32440↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-46058 · cve.blacktree.nl