high CVSS 7.8

CVE-2024-57798·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() While receiving an MST up request message from one thread in drm_dp_mst_handle_up_req(), the MST topology could be removed from another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing mst_primary and setting drm_dp_mst_topology_mgr::mst_primary to NULL. This could lead to a NULL deref/use-after-free of mst_primary in drm_dp_mst_handle_up_req(). Avoid the above by holding a reference for mst_primary in drm_dp_mst_handle_up_req() while it's used. v2: Fix kfreeing the request if getting an mst_primary reference fails.

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

Affected versions

From: 6.7

Until: 6.12.8

Fixed in: 6.12.8

How to fix this CVE

Update your Linux kernel to version 6.12.8 or later to patch a race condition in the DisplayPort MST (Multi-Stream Transport) handler that could cause kernel crashes or memory corruption. Systems running kernel versions 6.7 through 6.12.7 should prioritize this update to eliminate the risk of NULL pointer dereference when MST topology changes occur concurrently with message handling.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Run `uname -r` to check your current kernel version and confirm if it falls within 6.7.x to 6.12.7 range
  2. Execute `cat /proc/cmdline` to verify no custom kernel parameters are masking the vulnerability
  3. Check for DisplayPort MST devices with `lspci | grep -i display` or `lsmod | grep drm_dp_mst` to determine if the vulnerable code path is loaded
  4. After patching, run `uname -r` again and verify the kernel version is 6.12.8 or later, then reboot to activate the fixed kernel

FAQ

What is CVE-2024-57798?

This vulnerability is a race condition in the Linux kernel's DisplayPort MST subsystem where concurrent MST message processing and topology removal can trigger a NULL pointer dereference or use-after-free condition, potentially causing kernel crashes or data corruption.

Is CVE-2024-57798 being actively exploited?

No, this CVE is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, the high CVSS score of 7.8 indicates it should still be prioritized for patching.

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

Linux kernel versions 6.7.x through 6.12.7 are vulnerable. Version 6.12.8 and later contain the fix.

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

Run `uname -r` to display your kernel version; if it shows 6.7 through 6.12.7, your system is vulnerable and requires immediate update to 6.12.8 or newer.

Does Defensia detect CVE-2024-57798?

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

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

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

Get started free