LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can deadlock the system while KASAN is producing a memory error report. The business impact is mainly availability risk on affected kernels, especially debug or test kernels using KASAN. Public sources do not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patching where KASAN-enabled kernels support production-adjacent testing, CI reliability, or operational diagnostics, and fold remaining systems into normal vendor kernel update cycles.

Technical view

KASAN called kasan_find_vm_area(), which used find_vm_area() in an atomic context. The CVE describes a lock-order scenario involving vmap_area locks and softirq locking that can deadlock during KASAN report generation. Stable kernel commits remove kasan_find_vm_area() to avoid this path.

Likely exposure

Exposure is Linux systems running affected kernel versions or downstream packages identified by vendor advisories. The described trigger is tied to KASAN report handling, so environments with KASAN-enabled kernels are the clearest concern. The supplied data does not define CPEs or exact distribution package ranges beyond Debian LTS reference material.

Exploitation context

The source bundle does not identify public exploitation, weaponized proof of concept, or CISA KEV listing. The condition appears to require an invalid memory access that reaches KASAN reporting while relevant locks are held, creating a deadlock rather than direct code execution.

Researcher notes

The CVE record gives no CVSS, CWE, CPEs, or exploit confirmation. Analysis should focus on the KASAN reporting path, affected stable branches, and downstream backport status. Avoid broad claims about all Linux deployments unless vendor package data confirms exposure.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Follow Debian LTS or distribution-specific kernel advisory guidance.
  • Prioritize KASAN-enabled test, staging, and debug kernel environments.
  • Avoid assuming coverage from version numbers alone; confirm downstream backports.

Validation and detection

  • Inventory Linux kernel versions and distribution kernel package revisions.
  • Identify hosts or CI systems running kernels built with KASAN enabled.
  • Check vendor advisories for the referenced CVE or stable commit backports.
  • Confirm patched kernels no longer contain the vulnerable kasan_find_vm_area() reporting path.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38510 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc056a364e9546bd513d1f5205f0ee316d8acb910, c056a364e9546bd513d1f5205f0ee316d8acb910, c056a364e9546bd513d1f5205f0ee316d8acb910, c056a364e9546bd513d1f5205f0ee316d8acb910, c056a364e9546bd513d1f5205f0ee316d8acb910unaffected
LinuxLinux5.18, 0, 6.1.146, 6.6.99, 6.12.39, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.