CyberSecBulletin
CVE-2026-68273NVD status: Received

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-68273 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 ebed6179c993f07da24d0a454816e7da790377af, 3531910845165dcf1a213267199ccc97e03cd58a, 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a 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.13% 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 ebed6179c993f07da24d0a454816e7da790377af or 3531910845165dcf1a213267199ccc97e03cd58a or 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a or e06c39cc1c48dca68a5ffd971c23025a52d46634, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, ebed6179c993f07da24d0a454816e7da790377af; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, 3531910845165dcf1a213267199ccc97e03cd58a; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, e06c39cc1c48dca68a5ffd971c23025a52d46634; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, 9f9c88eb298c54348be3ca4087f4f4c615065b87; 79610d3041338dc1ef554d6fd8b3b3e23be527f5 up to, but not including, c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351; 6607901fce79959130db485e7549dacaaeef034e; 6.0.7 up to, but not including, 6.1; and 1 more rangesebed6179c993f07da24d0a454816e7da790377af, 3531910845165dcf1a213267199ccc97e03cd58a, 23a8726e1d7597fe7c9a59d5dc42ba8b7d345b8a, e06c39cc1c48dca68a5ffd971c23025a52d46634, 9f9c88eb298c54348be3ca4087f4f4c615065b87, c1dc4ccb82c9e56325d8e7514ca4c90bd1efb351

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: drm/amdgpu: Fix context pstate override handling There are several problems in the context pstate handling code. The most serious ones are potential use-after-free and NULL pointer dereferences at context initialization time. Both are due amdgpu_ctx_init() not holding the adev->pm.stable_pstate_ctx_lock, which is otherwise used from both sysfs and the context code itself for modifying and clearing the stored context pointer. Second issue is that context fini can trample over the pstate configuration set via sysfs. This is due the restore state (ctx->stable_pstate) being saved at context init time, and not if, or when the context actually changes the pstate. As the context exits it will therefore incorrectly restore to what was set before the sysfs override was requested. The simplest fix is to drastically simplify how the state is tracked, by clearly defining the points at which pstate ownership is taken and released, and to handle all transitions under the correct lock. Instead of at context init time, the previous state is saved only at the point the context overrides the current state, and is restored on context exit only if the context is still the owner of the current override state. (cherry picked from commit 1b5e413713c0a93bc1818394d0ce49aaad21bd27)

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. 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.