CVE-2024-35955 Details
Description
In the Linux kernel, the following vulnerability has been resolved: kprobes: Fix possible use-after-free issue on kprobe registration When unloading a module, its state is changing MODULE_STATE_LIVE -> MODULE_STATE_GOING -> MODULE_STATE_UNFORMED. Each change will take a time. `is_module_text_address()` and `__module_text_address()` works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use `is_module_text_address()` and `__module_text_address()` separately, there is a chance that the first one is succeeded but the next one is failed because module->state becomes MODULE_STATE_UNFORMED between those operations. In `check_kprobe_address_safe()`, if the second `__module_text_address()` is failed, that is ignored because it expected a kernel_text address. But it may have failed simply because module->state has been changed to MODULE_STATE_UNFORMED. In this case, arm_kprobe() will try to modify non-exist module text address (use-after-free). To fix this problem, we should not use separated `is_module_text_address()` and `__module_text_address()`, but use only `__module_text_address()` once and do `try_module_get(module)` which is only available with MODULE_STATE_LIVE.
A use-after-free vulnerability has been identified in the Linux kernel's kprobes functionality. This issue arises during the process of unloading a module, where the module's state transitions from 'live' to 'going' and finally to 'unformed'. This transition takes time, and the functions 'is_module_text_address()' and '__module_text_address()' can only be relied upon when the module is in the 'live' or 'going' states'. If these functions are called separately, the first call may succeed while the second fails, due to the module state changing to 'unformed'. This can lead to 'arm_kprobe()' attempting to modify a non-existent module text address, causing a use-after-free condition. The vulnerability can be exploited by manipulating module unloading and kprobe registration processes.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version of the kernel where this issue has been addressed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 20, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.14.291, < 4.15 >= 4.19.256, < 4.19.313 >= 5.4.211, < 5.4.275 >= 5.10.137, < 5.10.216 >= 5.15.61, < 5.15.157 >= 5.18.18, < 5.19 >= 5.19.2, < 6.1.87 >= 6.2, < 6.6.28 >= 6.7, < 6.8.7 6.9 rc1 6.9 rc2 6.9 rc3 |
CPE
Remediation
| |
| debian debian linux | 10.0 |
CPE
Remediation
| |
Change History
15 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | CVE |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | siemens-SADP |
| May 12, 2026 | CVE Modified | siemens-SADP |
| Apr 4, 2025 | Initial Analysis | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| Nov 5, 2024 | CVE Modified | kernel.org |
| Jul 3, 2024 | CVE Modified | CISA-ADP |
| Jun 27, 2024 | CVE Modified | kernel.org |
| Jun 25, 2024 | CVE Modified | kernel.org |
| May 29, 2024 | CVE Modified | kernel.org |
| May 20, 2024 | New CVE Received | kernel.org |