Skip to main content
VulnerabilityPublished Updated

CVE-2025-38510: Linux kernel · kasan: remove kasan_find_vm_area() to prevent possible deadlock

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc, 595f78d99b9051600233c0a5c4c47e1097e6ed01, 6ee9b3d84775944fb8c8a447961cd01274ac671c +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c056a364e9546bd513d1f5205f0ee316d8acb910, < 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc
Fixed in
  • 8377d7744bdce5c4b3f1b58924eebd3fdc078dfc
LinuxLinuxAffected
  • ≥ c056a364e9546bd513d1f5205f0ee316d8acb910, < 595f78d99b9051600233c0a5c4c47e1097e6ed01
Fixed in
  • 595f78d99b9051600233c0a5c4c47e1097e6ed01
LinuxLinuxAffected
  • ≥ c056a364e9546bd513d1f5205f0ee316d8acb910, < 6ee9b3d84775944fb8c8a447961cd01274ac671c
Fixed in
  • 6ee9b3d84775944fb8c8a447961cd01274ac671c
LinuxLinuxAffected
  • ≥ c056a364e9546bd513d1f5205f0ee316d8acb910, < 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9
Fixed in
  • 2d89dab1ea6086e6cbe6fe92531b496fb6808cb9
LinuxLinuxAffected
  • ≥ c056a364e9546bd513d1f5205f0ee316d8acb910, < 0c3566d831def922cd56322c772a7b20d8b0e0c0
Fixed in
  • 0c3566d831def922cd56322c772a7b20d8b0e0c0
LinuxLinuxAffected
  • =5.18
Fixed in–

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

References

Community reviews

Loading reviews…