CVE-2025-38102
VMCI: fix race between vmci_host_setup_notify and vmci_ctx_unset_notify
Reported by linux · Published July 3, 2025
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12 | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-devel | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-livepatch-6.1.144-170.251 | Amazon Linux | 1:1.0-0.amzn2023 |
| python3-perf | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-libbpf-devel | Amazon Linux | 6.12.35-55.103.amzn2023 |
| kernel-modules-extra | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| perf | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| kernel | Amazon Linux | 1:6.1.144-170.251.amzn2023 |
| kernel-livepatch-6.12.35-55.103 | Amazon Linux | 1.0-0.amzn2023 |
| Linux | Linux | 75b5313c80c39a26d27cbb602f968a05576c36f9, 6e3af836805ed1d7a699f76ec798626198917aa4, 1bd6406fb5f36c2bb1e96e27d4c3e9f4d09edde4 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc, a1d88436d53a75e950db15834b3d2f8c0c358fdc |
| Linux | Linux | 4.0, 0, 5.4.296 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel-livepatch-6.1.144-170.251 | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel-livepatch-6.12.35-55.103 | 0 |
| Linux | Linux | 0, *, * |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| linux | linux_kernel | 4.0, 4.0, 4.0 |
…and 3 more
Timeline
- Jul 2, 2025 CVE Published
- Jul 3, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (11 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (224 in total, the first dated here)
- Mar 29, 2026 Security Advisory (238 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38102
vulnetix vdb fixes CVE-2025-38102
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38102/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart