CyberSecBulletin
CVE-2025-38102NVD status: Modified

Linux: Concurrent Execution using Shared Resource with Improper Synchronization

Published Updated By the CyberSecBulletin desk

CVE-2025-38102 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 74095bbbb19ca74a0368d857603a2438c88ca86c, 468aec888f838ce5174b96e0cb4396790d6f60ca, b4209e4b778e4e57d0636e1c9fc07a924dbc6043 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.17% 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 74095bbbb19ca74a0368d857603a2438c88ca86c or 468aec888f838ce5174b96e0cb4396790d6f60ca or b4209e4b778e4e57d0636e1c9fc07a924dbc6043 or 58a90db70aa6616411e5f69d1982d9b1dd97d774, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.4.296 or 5.10.240 or 5.15.186 or 6.1.142, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxa1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 74095bbbb19ca74a0368d857603a2438c88ca86c; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 468aec888f838ce5174b96e0cb4396790d6f60ca; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, b4209e4b778e4e57d0636e1c9fc07a924dbc6043; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 58a90db70aa6616411e5f69d1982d9b1dd97d774; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 6e3af836805ed1d7a699f76ec798626198917aa4; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 00ddc7dad55b7bbb78df80d6e174d0c4764dea0c; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 75b5313c80c39a26d27cbb602f968a05576c36f9; a1d88436d53a75e950db15834b3d2f8c0c358fdc up to, but not including, 1bd6406fb5f36c2bb1e96e27d4c3e9f4d09edde4; and 1 more ranges74095bbbb19ca74a0368d857603a2438c88ca86c, 468aec888f838ce5174b96e0cb4396790d6f60ca, b4209e4b778e4e57d0636e1c9fc07a924dbc6043, 58a90db70aa6616411e5f69d1982d9b1dd97d774, 6e3af836805ed1d7a699f76ec798626198917aa4, 00ddc7dad55b7bbb78df80d6e174d0c4764dea0c
LinuxLinux Kernel4.0 up to, but not including, 5.4.296; 5.5 up to, but not including, 5.10.240; 5.11 up to, but not including, 5.15.186; 5.16 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.35.4.296, 5.10.240, 5.15.186, 6.1.142, 6.6.94, 6.12.34
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: VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify During our test, it is found that a warning can be trigger in try_grab_folio as follow: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1678 at mm/gup.c:147 try_grab_folio+0x106/0x130 Modules linked in: CPU: 0 UID: 0 PID: 1678 Comm: syz.3.31 Not tainted 6.15.0-rc5 #163 PREEMPT(undef) RIP: 0010:try_grab_folio+0x106/0x130 Call Trace: <TASK> follow_huge_pmd+0x240/0x8e0 follow_pmd_mask.constprop.0.isra.0+0x40b/0x5c0 follow_pud_mask.constprop.0.isra.0+0x14a/0x170 follow_page_mask+0x1c2/0x1f0 __get_user_pages+0x176/0x950 __gup_longterm_locked+0x15b/0x1060 ? gup_fast+0x120/0x1f0 gup_fast_fallback+0x17e/0x230 get_user_pages_fast+0x5f/0x80 vmci_host_unlocked_ioctl+0x21c/0xf80 RIP: 0033:0x54d2cd ---[ end trace 0000000000000000 ]--- Digging into the source, context->notify_page may init by get_user_pages_fast and can be seen in vmci_ctx_unset_notify which will try to put_page. However get_user_pages_fast is not finished here and lead to following try_grab_folio warning. The race condition is shown as follow: cpu0 cpu1 vmci_host_do_set_notify vmci_host_setup_notify get_user_pages_fast(uva, 1, FOLL_WRITE, &context->notify_page); lockless_pages_from_mm gup_pgd_range gup_huge_pmd // update &context->notify_page vmci_host_do_set_notify vmci_ctx_unset_notify notify_page = context->notify_page; if (notify_page) put_page(notify_page); // page is freed __gup_longterm_locked __get_user_pages follow_trans_huge_pmd try_grab_folio // warn here To slove this, use local variable page to make notify_page can be seen after finish get_user_pages_fast.

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.