Answer in brief
CVE-2024-35955 records a High severity (CVSS 8.8) vulnerability in kprobes: Fix possible use-after-free issue on kprobe registration. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), Siemens/RUGGEDCOM RST2428P (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1c836bad43f3e2ff71cc397a6e6ccb4e7bd116f8 <b5808d40093403334d939e2c3c417144d12a6f33 || >=6a119c1a584aa7a2c6216458f1f272bf1bc93a93 <93eb31e7c3399e326259f2caa17be1e821f5a412 || >=2a49b025c36ae749cee7ccc4b7e456e02539cdc3 <5062d1f4f07facbdade0f402d9a04a788f52e26d || >=a1edb85e60fdab1e14db63ae8af8db3f0d798fb6 <2df2dd27066cdba8041e46a64362325626bdfb2e || >=28f6c37a2910f565b4f5960df52b2eccae28c891 <62029bc9ff2c17a4e3a2478d83418ec575413808 || >=28f6c37a2910f565b4f5960df52b2eccae28c891 <d15023fb407337028a654237d8968fefdcf87c2f || >=28f6c37a2910f565b4f5960df52b2eccae28c891 <36b57c7d2f8b7de224980f1a284432846ad71ca0 || >=28f6c37a2910f565b4f5960df52b2eccae28c891 <325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8 || 4262b6eb057d86c7829168c541654fe0d48fdac8 || 97e813e6a143edf4208e15c72199c495ed80cea5 || 16a544f1e013ba0660612f3fe35393b143b19a84 || >=4.19.256 <4.19.313 || >=5.4.211 <5.4.275 || >=5.10.137 <5.10.216 || >=5.15.61 <5.15.157 || >=4.14.291 <4.15 || >=5.18.18 <5.19 || >=5.19.2 <5.20 | b5808d40093403334d939e2c3c417144d12a6f33, 93eb31e7c3399e326259f2caa17be1e821f5a412, 5062d1f4f07facbdade0f402d9a04a788f52e26d, 2df2dd27066cdba8041e46a64362325626bdfb2e, 62029bc9ff2c17a4e3a2478d83418ec575413808, d15023fb407337028a654237d8968fefdcf87c2f, 36b57c7d2f8b7de224980f1a284432846ad71ca0, 325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8, 4.19.313, 5.4.275, 5.10.216, 5.15.157, 4.15, 5.19, 5.20 |
| Linux/Linuxgeneric | 6.0 | Not reported |
| linux/linux_kernelgeneric | >=1c836bad43f3 <b5808d400934 || >=6a119c1a584a <93eb31e7c339 || >=2a49b025c36a <93eb31e7c339 || >=a1edb85e60fd <2df2dd27066c || >=28f6c37a2910 <62029bc9ff2c || >=28f6c37a2910 <d15023fb4073 || >=28f6c37a2910 <36b57c7d2f8b || >=28f6c37a2910 <325f3fb551f8 || 6.0 | b5808d400934, 93eb31e7c339, 2df2dd27066c, 62029bc9ff2c, d15023fb4073, 36b57c7d2f8b, 325f3fb551f8 |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.1 | V3.1 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.1 | V3.1 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
May 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.