high CVSS 7.8

CVE-2024-38581·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/mes: fix use-after-free issue Delete fence fallback timer to fix the ramdom use-after-free issue. v2: move to amdgpu_mes.c

Severity
high
Software
Kernel
Fixed in
6.8.12
Published
2024-06-19

Affected versions

From: 6.7

Until: 6.8.12

Fixed in: 6.8.12

How to fix this CVE

Update the Linux kernel to version 6.8.12 or later to resolve a use-after-free vulnerability in the AMD GPU Micro Engine Scheduler (MES) component. The vulnerability stems from improper fence fallback timer cleanup that could lead to memory corruption and system instability. Apply the kernel update through your distribution's package manager and reboot the system to activate the patched kernel.

sudo dnf update kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version with `uname -r` and verify if it falls within the vulnerable range (6.7 to 6.8.11)
  2. Step 2: Confirm AMD GPU presence by running `lspci | grep -i amd` to determine if the MES scheduler component is in use
  3. Step 3: Search system logs for MES-related errors using `sudo journalctl -xe | grep -i 'mes\|amdgpu' | grep -i 'error\|fault\|oops'`
  4. Step 4: After updating to kernel 6.8.12+, verify the fix with `uname -r` and check for absence of use-after-free errors in dmesg logs: `dmesg | grep -i 'use-after-free'`

FAQ

What is CVE-2024-38581?

CVE-2024-38581 is a use-after-free vulnerability in the Linux kernel's AMD GPU Micro Engine Scheduler (MES) that occurs when fence fallback timers are not properly deleted during cleanup operations. This memory safety issue can lead to kernel crashes, data corruption, or potential privilege escalation on systems with AMD GPUs.

Is CVE-2024-38581 being actively exploited?

No, CVE-2024-38581 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code has been released. However, the high CVSS score (7.8) warrants prompt patching due to the severity of use-after-free conditions.

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

Linux kernel versions 6.7 through 6.8.11 are affected. The vulnerability is fixed in kernel version 6.8.12 and later releases.

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

Run `uname -r` to display your kernel version. If the output shows a version between 6.7 and 6.8.11 and you have AMD GPUs, your system is vulnerable. Additionally, verify AMD GPU presence with `lspci | grep -i amd`.

Does Defensia detect CVE-2024-38581?

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-38581 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-2022-48716CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix incorrect used of portid Mixer controls have the channel id in mixer->reg, which is not same as port id. port id should be derived from chan_info array. So fix this. Without this, its possible that we could corrupt struct wcd938x_sdw_priv by accessing port_map array out of range with channel id instead of port id.

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

Get started free