high CVSS 7.8

CVE-2024-50051·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: spi: mpc52xx: Add cancel_work_sync before module remove If we remove the module which will call mpc52xx_spi_remove it will free 'ms' through spi_unregister_controller. while the work ms->work will be used. The sequence of operations that may lead to a UAF bug. Fix it by ensuring that the work is canceled before proceeding with the cleanup in mpc52xx_spi_remove.

Severity
high
Software
Kernel
Fixed in
6.12.5
Published
2025-01-11

Affected versions

From: 6.7

Until: 6.12.5

Fixed in: 6.12.5

How to fix this CVE

Update your Linux kernel to version 6.12.5 or later to patch a use-after-free vulnerability in the MPC52xx SPI driver. This vulnerability could allow local attackers with low privileges to cause system crashes or potentially execute code by triggering module removal while pending work operations are still scheduled. Apply the update promptly, especially on systems using MPC52xx SPI hardware.

sudo dnf upgrade kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your kernel version with: uname -r — compare against 6.12.5 or later
  2. Step 2: Determine if MPC52xx SPI driver is loaded with: lsmod | grep mpc52xx
  3. Step 3: Check kernel logs for use-after-free warnings with: dmesg | grep -i 'use.*after.*free\|uaf\|spi'
  4. Step 4: Verify the patch was applied by checking: grep -r 'cancel_work_sync' /usr/src/linux-headers-$(uname -r)/drivers/spi/spi-mpc52xx.c 2>/dev/null || echo 'Not patched'

FAQ

What is CVE-2024-50051?

CVE-2024-50051 is a use-after-free vulnerability in the Linux kernel's MPC52xx SPI driver that occurs when the module is removed while internal work queue operations are still pending, potentially leading to memory corruption or denial of service.

Is CVE-2024-50051 being actively exploited?

No, CVE-2024-50051 is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available, though the vulnerability requires local system access to exploit.

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

Linux kernel versions 6.7 through 6.12.4 are affected; the vulnerability is patched in kernel 6.12.5 and later.

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

Run: uname -r — if the output shows kernel version between 6.7 and 6.12.4, you are vulnerable. Additionally, check if MPC52xx SPI hardware is in use on your system with: lspci | grep -i spi or lsmod | grep mpc52xx.

Does Defensia detect CVE-2024-50051?

Yes — Defensia's CVE advisory scanner compares installed kernel versions against the NVD database. If a vulnerable kernel version is detected on a monitored server, CVE-2024-50051 will appear in your dashboard with remediation steps and prioritization guidance.

Related Kernel CVEs

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-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-64066CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_read_to_pagecache() to pause on subreq failure Fix netfs_read_to_pagecache() so that it pauses the generation of new subrequests if an already-issued subrequest fails.
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-64067CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing barriers when accessing stream->subrequests locklessly The list of subrequests attached to stream->subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq->flags without taking a barrier after getting the subreq pointer from the list. Relatedly, the functions that build the list don't use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by: (1) Add a new list_add_tail_release() function that uses a release barrier to set the pointer to the new member of the list. (2) Add a new list_first_entry_or_null_acquire() function that uses an acquire barrier to read the pointer to the first member in a list (or return NULL). (3) Use list_add_tail_release() when adding a subreq to ->subrequests. (4) Use list_first_entry_or_null_acquire() when initially accessing the front of the list (when an item is removed, the pointer to the new front iterm is obtained under the same lock).

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-50051. Free for 1 server.

Get started free