CyberSecBulletin
CVE-2026-53354NVD status: Modified

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-53354 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 8.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 925058203229403008d77a52b1e63e2ae5f4a3cf, 8364384ae82fbffdf8968abaac3455ed854da18d, 7c3ad9365079e716b57d2363d3081ee7680cc18e 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 925058203229403008d77a52b1e63e2ae5f4a3cf or 8364384ae82fbffdf8968abaac3455ed854da18d or 7c3ad9365079e716b57d2363d3081ee7680cc18e or e717a4d08779f1a28d6e0275e75040b12c33c753, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 925058203229403008d77a52b1e63e2ae5f4a3cf; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 8364384ae82fbffdf8968abaac3455ed854da18d; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 7c3ad9365079e716b57d2363d3081ee7680cc18e; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, e717a4d08779f1a28d6e0275e75040b12c33c753; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, d4fd4282204044fdedd1e42abbe70a9206f74ec0; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 1b47b1e1d8675fdf5f6e11e7fa19c704d8c6f5cd; 58d0ba578bc3b7c044d4ef570307bcb03862cb66 up to, but not including, 1268c64e2bcb6e968152990e87bd10c440fcc9c0; and 2 more ranges925058203229403008d77a52b1e63e2ae5f4a3cf, 8364384ae82fbffdf8968abaac3455ed854da18d, 7c3ad9365079e716b57d2363d3081ee7680cc18e, e717a4d08779f1a28d6e0275e75040b12c33c753, 4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8, d4fd4282204044fdedd1e42abbe70a9206f74ec0
LinuxLinux Kernel3.7 up to, but not including, 5.10.259; 5.11 up to, but not including, 5.15.210; 5.16 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 up to, but not including, 7.1.15.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36

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
ChangedThe attack can reach beyond the vulnerable component into other systems.
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:C/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: arm64: errata: Mitigate TLBI errata on various Arm CPUs A number of CPUs developed by Arm suffer from errata whereby a broadcast TLBI;DSB sequence may complete before the global observation of writes which are translated by an affected TLB entry. These errata ONLY affect the completion of memory accesses which have been translated by an invalidated TLB entry, and these errata DO NOT affect the actual invalidation of TLB entries. TLB entries are removed correctly. This issue has been assigned CVE ID CVE-2025-10263. To mitigate this issue, Arm recommends that software follows any affected TLBI;DSB sequence with an additional TLBI;DSB, which will ensure that all memory write effects affected by the first TLBI have been globally observed. The additional TLBI can use any operation that is broadcast to affected CPUs, and the additional DSB can use any option that is sufficient to complete the additional TLBI. The ARM64_WORKAROUND_REPEAT_TLBI workaround is sufficient to mitigate the issue. Enable this workaround for affected CPUs, and update the silicon errata documentation accordingly. Note that due to the manner in which Arm develops IP and tracks errata, some CPUs share a common erratum number.

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.