CVE-2024-35955: Linux kernel · kprobes: Fix possible use-after-free issue on kprobe registration
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 8.8 High · fixed in 4.15.0-1180.195~14.04.1 : patch Linux kernel soon.
Data as of 12 Nov 2026, 19:04 UTC
- Patch
- Available – fixed in 4.15.0-1180.195~14.04.1, 4.15.0-1172.185~16.04.1, 4.15.0-1180.195~16.04.1 +84
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6893-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-4 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-35955 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-35955 (opens in a new tab)
- git.kernel.org/linus/325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8 (opens in a new tab)
- git.kernel.org/stable/c/b5808d40093403334d939e2c3c417144d12a6f33 (opens in a new tab)
- git.kernel.org/stable/c/93eb31e7c3399e326259f2caa17be1e821f5a412 (opens in a new tab)
- git.kernel.org/stable/c/5062d1f4f07facbdade0f402d9a04a788f52e26d (opens in a new tab)
- git.kernel.org/stable/c/2df2dd27066cdba8041e46a64362325626bdfb2e (opens in a new tab)
- git.kernel.org/stable/c/62029bc9ff2c17a4e3a2478d83418ec575413808 (opens in a new tab)
- git.kernel.org/stable/c/d15023fb407337028a654237d8968fefdcf87c2f (opens in a new tab)
- git.kernel.org/stable/c/36b57c7d2f8b7de224980f1a284432846ad71ca0 (opens in a new tab)
- git.kernel.org/stable/c/325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6893-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6898-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6896-4 (opens in a new tab)