medium CVSS 5.5

CVE-2024-38615·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: cpufreq: exit() callback is optional The exit() callback is optional and shouldn't be called without checking a valid pointer first. Also, we must clear freq_table pointer even if the exit() callback isn't present.

Severity
medium
Software
Kernel
Fixed in
6.9.3
Published
2024-06-19

Affected versions

From: 6.9

Until: 6.9.3

Fixed in: 6.9.3

How to fix this CVE

Update your Linux kernel to version 6.9.3 or later to address a resource management flaw in the cpufreq subsystem. The vulnerability stems from improper pointer validation when invoking optional driver callbacks, which can lead to denial of service conditions. Ensure kernel updates are applied and the system is rebooted to activate the patched version.

sudo dnf update kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check your kernel version: uname -r | grep -E '^6\.9\.[0-2]' (returns match if vulnerable)
  2. Verify cpufreq module is loaded: lsmod | grep cpufreq (confirms module presence)
  3. Review cpufreq driver details: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver (identifies active driver)
  4. Confirm patch application: uname -r | grep -E '^6\.9\.[3-9]' or grep -i 'cpufreq.*exit' /proc/version (should not match vulnerable pattern post-patch)

FAQ

What is CVE-2024-38615?

This CVE describes a kernel cpufreq subsystem defect where optional driver exit callbacks are invoked without validating pointer validity, and frequency table pointers are not properly cleared. This can cause a denial of service when the affected code path is triggered.

Is CVE-2024-38615 being actively exploited?

No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and has no publicly available exploit code. However, the medium CVSS score and local attack vector warrant timely patching.

What versions of Kernel are affected by CVE-2024-38615?

Kernel versions 6.9 through 6.9.2 are vulnerable. The fix is included in version 6.9.3 and all subsequent releases.

How do I check if my server is vulnerable to CVE-2024-38615?

Run 'uname -r' and check if the output shows kernel 6.9.0, 6.9.1, or 6.9.2. If so, your system requires immediate patching.

Does Defensia detect CVE-2024-38615?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-38615 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-64439CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: crypto: krb5 - filter out async aead implementations at alloc krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL completion callback and treat any negative return from crypto_aead_{encrypt,decrypt}() as terminal, falling through to kfree_sensitive(buffer). When the encrypt_name resolves to an async AEAD instance the request returns -EINPROGRESS, the buffer is freed while the backend's worker still holds a pointer, and the worker dereferences the freed slab on completion. KASAN report under UML+SLUB with a synthetic async aead backend bound to krb5->encrypt_name: BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7 The helpers were written synchronously, so filter the async instances out at allocation time instead of plumbing crypto_wait_req() through every call site. Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and net/ceph/crypto.c on systems with an async AEAD provider bound to the krb5 enctype name.
CVE-2026-100075CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contexts but leaves stale n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending() can then subtract the wrong number of send queue credits. Reset the counters and clear rw_ctxs after freeing the heap allocation before returning an error.
CVE-2026-64383CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
CVE-2026-64385CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_ioctl() replay A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_ioctl_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.
CVE-2026-64384CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix change notify replay double-free A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_notify_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-38615. Free for 1 server.

Get started free