CyberSecBulletin
CVE-2026-72024NVD status: Received

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2026-72024 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 72ac5af9ad09662bd0ea91cb8845d490c8ef9c01, 2039f27b1a0c997137a5de7f8a3cee0e80fbf952, 4bf231f459b542414629b64f63d5cad6701bd07c 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 72ac5af9ad09662bd0ea91cb8845d490c8ef9c01 or 2039f27b1a0c997137a5de7f8a3cee0e80fbf952 or 4bf231f459b542414629b64f63d5cad6701bd07c or b91e5248dd7af09b500879a46d22a36b60db3a57, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, 72ac5af9ad09662bd0ea91cb8845d490c8ef9c01; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, 2039f27b1a0c997137a5de7f8a3cee0e80fbf952; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, 4bf231f459b542414629b64f63d5cad6701bd07c; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, b91e5248dd7af09b500879a46d22a36b60db3a57; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, c7c031b75218b3ba3014a0f6b9849888994528d6; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, 77caf2d6eba7cb94a7ecd7b369a5974fd7d7c054; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, d8b5b66388a51febe4b8505b0ecd9da15b4ba639; 592dfbfc72f5352437c883aa11ab579d10cdb595 up to, but not including, 539dfcf69105d8d3d4d677b71de6e5ede2e6dfa0; and 1 more ranges72ac5af9ad09662bd0ea91cb8845d490c8ef9c01, 2039f27b1a0c997137a5de7f8a3cee0e80fbf952, 4bf231f459b542414629b64f63d5cad6701bd07c, b91e5248dd7af09b500879a46d22a36b60db3a57, c7c031b75218b3ba3014a0f6b9849888994528d6, 77caf2d6eba7cb94a7ecd7b369a5974fd7d7c054

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: mac802154: remove interfaces with RCU list deletion Queue wake, stop, and disable paths walk local->interfaces under RCU. The bulk hardware teardown path removes entries with list_del(), so an asynchronous transmit completion can follow a poisoned list node in ieee802154_wake_queue(). Use list_del_rcu() as in the single-interface removal path. The following unregister_netdevice() waits for in-flight RCU readers before freeing the netdevice, so no separate grace-period wait is needed.

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.