Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-38102

7.8 · HIGH

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 trig…

Published Jul 3, 2025CWE-362EPSS 0.16%

Overview

CVE-2025-38102 is a high-severity vulnerability. It was published on July 3, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_use

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/00ddc7dad55b7bbb78df80d6e174d0c4764dea0cRefgit.kernel.org/stable/c/1bd6406fb5f36c2bb1e96e27d4c3e9f4d09edde4Refgit.kernel.org/stable/c/468aec888f838ce5174b96e0cb4396790d6f60caRefgit.kernel.org/stable/c/58a90db70aa6616411e5f69d1982d9b1dd97d774Refgit.kernel.org/stable/c/6e3af836805ed1d7a699f76ec798626198917aa4Refgit.kernel.org/stable/c/74095bbbb19ca74a0368d857603a2438c88ca86cRefgit.kernel.org/stable/c/75b5313c80c39a26d27cbb602f968a05576c36f9Refgit.kernel.org/stable/c/b4209e4b778e4e57d0636e1c9fc07a924dbc6043Reflists.debian.org/debian-lts-announce/2025/10/msg00007.htmlReflists.debian.org/debian-lts-announce/2025/10/msg00008.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-38102?

CVE-2025-38102 is a high-severity vulnerability. It was published on July 3, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-38102?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-38102?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38102?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38102 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999