CyberSecBulletin
CVE-2026-46058NVD status: Analyzed

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-46058 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 516467052fdfc6a13eadc70d43420ae57436bf3c, 42dc622776f3ce1a6c31b13bdc686f7295e3b323, da4f46c5cf1d26e6b09418ad453e152f2e75a02c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 516467052fdfc6a13eadc70d43420ae57436bf3c or 42dc622776f3ce1a6c31b13bdc686f7295e3b323 or da4f46c5cf1d26e6b09418ad453e152f2e75a02c or fdc150dac1adb9a98be9d6956cff0348838b024a, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.175 or 6.6.140 or 6.12.86 or 6.18.27, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, 516467052fdfc6a13eadc70d43420ae57436bf3c; 3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, 42dc622776f3ce1a6c31b13bdc686f7295e3b323; 3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, da4f46c5cf1d26e6b09418ad453e152f2e75a02c; 3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, fdc150dac1adb9a98be9d6956cff0348838b024a; 3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, 6be2cb75bc1300080cfc8051579f22efae9401f7; 3cd084519c6f91cbef9d604bcf26844fa81d4922 up to, but not including, 8cd35ceadcfc8c5da2eb7f7ce24525ce9d4ee62e; 5.18516467052fdfc6a13eadc70d43420ae57436bf3c, 42dc622776f3ce1a6c31b13bdc686f7295e3b323, da4f46c5cf1d26e6b09418ad453e152f2e75a02c, fdc150dac1adb9a98be9d6956cff0348838b024a, 6be2cb75bc1300080cfc8051579f22efae9401f7, 8cd35ceadcfc8c5da2eb7f7ce24525ce9d4ee62e
LinuxLinux Kernel5.18 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.140; 6.7 up to, but not including, 6.12.86; 6.13 up to, but not including, 6.18.27; 6.19 up to, but not including, 7.0.46.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Official 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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization

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 developers prevent this class of flaw

  • In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Use thread-safe capabilities such as the data access abstraction in Spring.
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.