CVE-2025-38510
Last modified
CVE-2025-38510 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: kasan: remove kasan_find_vm_area() to prevent possible deadlock find_vm_area() couldn't be called in atomic_context. If find_vm_area() is called to reports vm area information, kasan can trigger deadlock like: CPU0 CPU1 vmalloc(); alloc_vmap_area(); spin_lock(&vn->busy.lock) spin_lock_bh(&some_lock); <interrupt occurs> <in softirq> spin_lock(&some_lock); <access invalid address> kasan_report(); print_report(); print_address_description(); kasan_find_vm_area(); find_vm_area(); spin_lock(&vn->busy.lock) // deadlock! To prevent possible deadlock while kasan reports, remove kasan_find_vm_area().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.18, < 6.1.146 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.99 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.39 | — |
| Linux | Linux Kernel | >= 6.13, < 6.15.7 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38510?
How severe is CVE-2025-38510?
How do I fix CVE-2025-38510?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38505In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38506In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38507In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38508In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38509In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3851The Download Manager and Payment Form WordPress Plugin – WP …4.3
- CVE-2025-38511In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38512In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38513In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38514In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38515In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38516In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38510?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST