Answer in brief
CVE-2025-38510 records a Medium severity (CVSS 5.5) vulnerability in kasan: remove kasan_find_vm_area() to prevent possible deadlock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c056a364e9546bd513d1f5205f0ee316d8acb910 <595f78d99b9051600233c0a5c4c47e1097e6ed01 || >=c056a364e9546bd513d1f5205f0ee316d8acb910 <8377d7744bdce5c4b3f1b58924eebd3fdc078dfc || >=c056a364e9546bd513d1f5205f0ee316d8acb910 <2d89dab1ea6086e6cbe6fe92531b496fb6808cb9 || >=c056a364e9546bd513d1f5205f0ee316d8acb910 <0c3566d831def922cd56322c772a7b20d8b0e0c0 || >=c056a364e9546bd513d1f5205f0ee316d8acb910 <6ee9b3d84775944fb8c8a447961cd01274ac671c | 595f78d99b9051600233c0a5c4c47e1097e6ed01, 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc, 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9, 0c3566d831def922cd56322c772a7b20d8b0e0c0, 6ee9b3d84775944fb8c8a447961cd01274ac671c |
| Linux/Linuxgeneric | 5.18 | Not reported |
Published upstream
Aug 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.