high CVSS 7.8

CVE-2024-53098·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/xe/ufence: Prefetch ufence addr to catch bogus address access_ok() only checks for addr overflow so also try to read the addr to catch invalid addr sent from userspace. (cherry picked from commit 9408c4508483ffc60811e910a93d6425b8e63928)

Severity
high
Software
Kernel
Fixed in
6.11.9
Published
2024-11-25

Affected versions

Until: 6.11.9

Fixed in: 6.11.9

How to fix this CVE

Update your Linux kernel to version 6.11.9 or later to remediate CVE-2024-53098, a local privilege escalation vulnerability in the DRM/xe driver's user fence handling. The fix adds address validation to prevent unprivileged users from passing bogus memory addresses that could bypass access control checks. Apply the update immediately if you are running an affected kernel version.

sudo dnf update kernel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your kernel version by running: `uname -r` — compare the output against 6.11.9
  2. Step 2: Verify if the xe DRM driver is loaded: `lsmod | grep xe` — if present, your system may be vulnerable
  3. Step 3: Search kernel logs for user fence-related errors: `dmesg | grep -i ufence` or `journalctl -g ufence`
  4. Step 4: After patching, reboot and confirm the new kernel version: `uname -r` should show 6.11.9 or higher

FAQ

What is CVE-2024-53098?

CVE-2024-53098 is a local privilege escalation vulnerability in the Linux kernel's DRM/xe driver. A local attacker with user privileges can pass invalid memory addresses to the user fence handler, bypassing address validation and potentially gaining elevated access.

Is CVE-2024-53098 being actively exploited?

No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been disclosed as of the time of this advisory.

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

All Linux kernel versions up to and including 6.11.8 are affected. The vulnerability has been patched in kernel version 6.11.9 and later.

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

Run `uname -r` to see your kernel version. If it is older than 6.11.9 and the xe DRM driver is present (`lsmod | grep xe`), your system is vulnerable.

Does Defensia detect CVE-2024-53098?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-53098 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-53098. Free for 1 server.

Get started free