high CVSS 7.1

CVE-2024-50193·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: x86/entry_32: Clear CPU buffers after register restore in NMI return CPU buffers are currently cleared after call to exc_nmi, but before register state is restored. This may be okay for MDS mitigation but not for RDFS. Because RDFS mitigation requires CPU buffers to be cleared when registers don't have any sensitive data. Move CLEAR_CPU_BUFFERS after RESTORE_ALL_NMI.

Severity
high
Software
Kernel
Fixed in
6.11.5
Published
2024-11-08

Affected versions

From: 6.8

Until: 6.11.5

Fixed in: 6.11.5

How to fix this CVE

Update your Linux kernel to version 6.11.5 or later to address this CPU buffer clearing vulnerability that affects x86-32 NMI handling. This patch repositions buffer mitigation logic to occur after register state restoration, ensuring proper defense against RDFS (Register Data Sampling) attacks. Systems running kernel versions 6.8 through 6.11.4 should prioritize this update, followed by a reboot to activate the patched kernel.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed kernel version: uname -r | grep -E '^(6\.(8|9|10|11\.[0-4]))'
  2. Verify x86-32 architecture exposure: uname -m | grep -i 'i386\|i686'
  3. Review NMI-related CPU buffer operations in dmesg: dmesg | grep -i 'nmi\|cpu.*buffer\|rdfs'
  4. Confirm patch applied by checking kernel config: grep -i 'clear_cpu_buffers' /boot/config-$(uname -r) && uname -r | grep -E '6\.11\.5|6\.12|[7-9]\.'
  5. Validate fix with sysfs inspection: cat /proc/cmdline | grep -i 'mds\|rdfs' to see active mitigations

FAQ

What is CVE-2024-50193?

This vulnerability affects the Linux kernel's x86-32 NMI (Non-Maskable Interrupt) exception handler, where CPU buffer clearing for speculative execution mitigation occurs at the wrong time—before register state is restored. This timing flaw weakens protection against RDFS attacks, which could theoretically leak sensitive register contents through CPU microarchitectural side-channels.

Is CVE-2024-50193 being actively exploited?

No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the high CVSS score (7.1) reflects its potential impact on system security posture.

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

Linux kernel versions 6.8.0 through 6.11.4 are vulnerable. Version 6.11.5 and all later versions include the fix.

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

Run 'uname -r' and check if the output matches the range 6.8.* through 6.11.4. If it does, and your system runs a 32-bit x86 architecture (check with 'uname -m'), your system is vulnerable.

Does this vulnerability require user interaction to exploit?

No—the CVSS vector shows PR:L (low privilege required) and UI:N (no user interaction), meaning a local attacker with basic permissions can trigger NMI conditions to attempt exploitation without user awareness.

Does Defensia detect CVE-2024-50193?

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

Get started free