---
id: CVE-2025-38510
title: 'kasan: remove kasan_find_vm_area() to prevent possible deadlock'
summary: |-
  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 in…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 <
    595f78d99b9051600233c0a5c4c47e1097e6ed01
  - >-
    Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 <
    8377d7744bdce5c4b3f1b58924eebd3fdc078dfc
  - >-
    Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 <
    2d89dab1ea6086e6cbe6fe92531b496fb6808cb9
  - >-
    Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 <
    0c3566d831def922cd56322c772a7b20d8b0e0c0
  - >-
    Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 <
    6ee9b3d84775944fb8c8a447961cd01274ac671c
  - Linux 5.18
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:57:40.732785Z'
published: '2025-08-16'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T21:02:40.379Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2025-38510'
references:
  - url: 'https://git.kernel.org/stable/c/595f78d99b9051600233c0a5c4c47e1097e6ed01'
  - url: 'https://git.kernel.org/stable/c/8377d7744bdce5c4b3f1b58924eebd3fdc078dfc'
  - url: 'https://git.kernel.org/stable/c/2d89dab1ea6086e6cbe6fe92531b496fb6808cb9'
  - url: 'https://git.kernel.org/stable/c/0c3566d831def922cd56322c772a7b20d8b0e0c0'
  - url: 'https://git.kernel.org/stable/c/6ee9b3d84775944fb8c8a447961cd01274ac671c'
tags:
  - cve.org
epss: 0.00166
epssPercentile: 0.05831
ingestedAt: '2026-11-05T22:38:31.975Z'
---

## Overview

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

- `Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 < 595f78d99b9051600233c0a5c4c47e1097e6ed01`
- `Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 < 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc`
- `Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 < 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9`
- `Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 < 0c3566d831def922cd56322c772a7b20d8b0e0c0`
- `Linux >= c056a364e9546bd513d1f5205f0ee316d8acb910 < 6ee9b3d84775944fb8c8a447961cd01274ac671c`
- `Linux 5.18`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.