CyberSecBulletin
CVE-2025-38107NVD status: Modified

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2025-38107 is a high-severity concurrent execution using shared resource with improper synchronization vulnerability in Linux, with a CVSS 3.1 base score of 7.0 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 eb7b74e9754e1ba2088f914ad1f57a778b11894b, 0b479d0aa488cb478eb2e1d8868be946ac8afb4f, 347867cb424edae5fec1622712c8dd0a2c42918f 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.16% 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 eb7b74e9754e1ba2088f914ad1f57a778b11894b or 0b479d0aa488cb478eb2e1d8868be946ac8afb4f or 347867cb424edae5fec1622712c8dd0a2c42918f or 0383b25488a545be168744336847549d4a2d3d6c, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.5 or 5.10.239 or 5.15.186 or 6.0, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux699d82e9a6db29d509a71f1f2f4316231e6232e6 up to, but not including, eb7b74e9754e1ba2088f914ad1f57a778b11894b; ce881ddbdc028fb1988b66e40e45ca0529c23b46 up to, but not including, 0b479d0aa488cb478eb2e1d8868be946ac8afb4f; b05972f01e7d30419987a1f221b5593668fd6448 up to, but not including, 347867cb424edae5fec1622712c8dd0a2c42918f; b05972f01e7d30419987a1f221b5593668fd6448 up to, but not including, 0383b25488a545be168744336847549d4a2d3d6c; b05972f01e7d30419987a1f221b5593668fd6448 up to, but not including, 073f64c03516bcfaf790f8edc772e0cfb8a84ec3; b05972f01e7d30419987a1f221b5593668fd6448 up to, but not including, fed94bd51d62d2e0e006aa61480e94e5cd0582b0; b05972f01e7d30419987a1f221b5593668fd6448 up to, but not including, d92adacdd8c2960be856e0b82acc5b7c5395fddb; fffa19b5e58c34004a0d6f642d9c24b11d213994; and 6 more rangeseb7b74e9754e1ba2088f914ad1f57a778b11894b, 0b479d0aa488cb478eb2e1d8868be946ac8afb4f, 347867cb424edae5fec1622712c8dd0a2c42918f, 0383b25488a545be168744336847549d4a2d3d6c, 073f64c03516bcfaf790f8edc772e0cfb8a84ec3, fed94bd51d62d2e0e006aa61480e94e5cd0582b0
LinuxLinux Kernel5.4.213 up to, but not including, 5.5; 5.10.142 up to, but not including, 5.10.239; 5.15.66 up to, but not including, 5.15.186; 5.19.8 up to, but not including, 6.0; 6.0.1 up to, but not including, 6.1.142; 6.2 up to, but not including, 6.6.94; 6.7 up to, but not including, 6.12.34; 6.13 up to, but not including, 6.15.3; and 2 more ranges5.5, 5.10.239, 5.15.186, 6.0, 6.1.142, 6.6.94
DebianDebian Linux11.0Not stated

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
HighSuccess depends on conditions outside the attacker's control.
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.0HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: net_sched: ets: fix a race in ets_qdisc_change() Gerrard Tai reported a race condition in ETS, whenever SFQ perturb timer fires at the wrong time. The race is as follows: CPU 0 CPU 1 [1]: lock root [2]: qdisc_tree_flush_backlog() [3]: unlock root | | [5]: lock root | [6]: rehash | [7]: qdisc_tree_reduce_backlog() | [4]: qdisc_put() This can be abused to underflow a parent's qlen. Calling qdisc_purge_queue() instead of qdisc_tree_flush_backlog() should fix the race, because all packets will be purged from the qdisc before releasing the lock.

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

Third-party and government advisories

Recent Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.