CVE-2025-38245
BaseFortify
Publication date: 2025-07-09
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 2.6.15 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 6.7 (inc) to 6.12.36 (inc) |
| debian | debian_linux | 11.0 |
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves a race condition related to the atm_dev_mutex mutex in the ATM device registration and deregistration process. Specifically, when removing a device (atm_dev_deregister), the mutex is released immediately after removing the device from the list, but before procfs/sysfs entries are removed. This creates a small window where the device is no longer in the list but its procfs/sysfs entries still exist, which can cause a system warning or crash (splat). The fix is to hold the mutex until after procfs/sysfs entries are removed to prevent this race condition.
How can this vulnerability impact me? :
This vulnerability can lead to system instability or crashes due to the race condition when removing ATM devices. The race window may cause kernel warnings or splats, potentially affecting system reliability and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for warnings related to procfs registration errors, specifically messages like 'proc_dir_entry 'atm/atmtcp:0' already registered' and warnings from proc_register in fs/proc/generic.c. You can check the kernel logs using commands such as 'dmesg | grep proc_register' or 'journalctl -k | grep proc_register' to identify these warnings.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, which includes the change to hold the atm_dev_mutex until procfs/sysfs are removed in atm_dev_deregister(). Until then, monitoring for the warning messages and avoiding operations that trigger atm device deregistration may reduce risk.