CyberSecBulletin
CVE-2026-72009NVD status: Received

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-72009 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 73c0d6957811d7c138124107e1d31e8fb0133156, 94b8a47f45f19c537964355fa539670631882b20, 4fd5b33faf092ef2d09f730a7d9e49f9e976ac67 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.14% 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 73c0d6957811d7c138124107e1d31e8fb0133156 or 94b8a47f45f19c537964355fa539670631882b20 or 4fd5b33faf092ef2d09f730a7d9e49f9e976ac67 or 4ba6d7166750d0b810c6cfc0b1df7585f513b48c, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe9aa77d413c903ba4cf7da3fe0b419cae5b97a81 up to, but not including, 73c0d6957811d7c138124107e1d31e8fb0133156; e9aa77d413c903ba4cf7da3fe0b419cae5b97a81 up to, but not including, 94b8a47f45f19c537964355fa539670631882b20; e9aa77d413c903ba4cf7da3fe0b419cae5b97a81 up to, but not including, 4fd5b33faf092ef2d09f730a7d9e49f9e976ac67; e9aa77d413c903ba4cf7da3fe0b419cae5b97a81 up to, but not including, 4ba6d7166750d0b810c6cfc0b1df7585f513b48c; e9aa77d413c903ba4cf7da3fe0b419cae5b97a81 up to, but not including, 99611233f8cda833169fa6487d5dacdf189e5cb0; 6.173c0d6957811d7c138124107e1d31e8fb0133156, 94b8a47f45f19c537964355fa539670631882b20, 4fd5b33faf092ef2d09f730a7d9e49f9e976ac67, 4ba6d7166750d0b810c6cfc0b1df7585f513b48c, 99611233f8cda833169fa6487d5dacdf189e5cb0

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: pmdomain: imx93-blk-ctrl: Extract PHY as shared domain for DSI/CSI The MIPI DSI and CSI domains share control bits for clock and reset, which can lead to incorrect behavior if one domain disables the shared resource while the other is still active. To fix the issue, introduce a shared MIPI PHY power domain to own the common resources and make DSI and CSI its subdomains. This ensures the shared bits are properly managed and not disabled while still in use.

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.