ZeroDay Findings
Sign inSign up

Findings

CVE-2024-35955

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 stat…

Published May 20, 2024 · updated Oct 15, 2026 · linux linux kernel

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. and works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use and 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 , if the second 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 and , but use only once and do which is only available with MODULE_STATE_LIVE.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 20, 2024 · NIST NVD

    Detected

    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. and works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use and separately, there is a chance that the first one is

  2. Oct 15, 2026 · NIST NVD

    Updated

    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. and works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use and separately, there is a chance that the first one is

Affected

  • cpe debian/debian linux10.0
  • cpe linux/linux kernelversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2024-35955

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2024-35955

    30-day exploitation probability 1.2%

    first.org
  • NIST NVDVulnerability recordCVE-2024-35955

    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.

    nvd.nist.gov

References