CVE-2025-38510

kasan: remove kasan_find_vm_area() to prevent possible deadlock

MEDIUM
5.5
CVSS Score
Published: August 16, 2025 at 10:54 AM UTC
Updated: June 17, 2026 at 09:17 AM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.1465.18 ≤ v < 6.12.395.18 ≤ v < 6.15.75.18 ≤ v < 6.165.18 ≤ v < 6.6.996.13 ≤ v < 6.15.76.2 ≤ v < 6.6.996.7 ≤ v < 6.12.395.186.16 rc16.16 rc26.16 rc36.16 rc46.16 rc5c056a364e9546bd513d1f5205f0ee316d8acb910
Vendor states this is fixed in 0c3566d831def922cd56322c772a7b20d8b0e0c0 (fixed)
Vendor states this is fixed in 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9 (fixed)
Vendor states this is fixed in 595f78d99b9051600233c0a5c4c47e1097e6ed01 (fixed)
Vendor states this is fixed in 6ee9b3d84775944fb8c8a447961cd01274ac671c (fixed)
Vendor states this is fixed in 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.146 (unaffected)
Vendor states this is fixed in 6.12.39 (unaffected)
Vendor states this is fixed in 6.15.7 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.6.99 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0c3566d831def922cd56322c772a7b20d8b0e0c0
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2d89dab1ea6086e6cbe6fe92531b496fb6808cb9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/595f78d99b9051600233c0a5c4c47e1097e6ed01
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6ee9b3d84775944fb8c8a447961cd01274ac671c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8377d7744bdce5c4b3f1b58924eebd3fdc078dfc
Mailing ListThird Party Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card