high CVSS 7

CVE-2024-43883·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: usb: vhci-hcd: Do not drop references before new references are gained At a few places the driver carries stale pointers to references that can still be used. Make sure that does not happen. This strictly speaking closes ZDI-CAN-22273, though there may be similar races in the driver.

Severity
high
Software
Kernel
Fixed in
6.10.5
Published
2024-08-23

Affected versions

From: 6.7

Until: 6.10.5

Fixed in: 6.10.5

How to fix this CVE

Update your Linux kernel to version 6.10.5 or later to resolve a race condition in the USB vhci-hcd driver that could allow reference counting vulnerabilities. This patch ensures that stale pointers are not retained when transitioning between reference states, preventing potential use-after-free conditions. Reboot your system after applying the kernel update.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version by running `uname -r` and compare it against the affected range (6.7 to 6.10.4)
  2. Step 2: Verify if USB vhci-hcd module is loaded by running `lsmod | grep vhci_hcd` — if present, the vulnerable component is active
  3. Step 3: Search system logs for USB-related errors using `dmesg | grep -i vhci` or `journalctl -u kernel | grep -i vhci` to identify any anomalous behavior
  4. Step 4: After patching, confirm the new kernel is booted with `uname -r` and verify it shows version 6.10.5 or later

FAQ

What is CVE-2024-43883?

CVE-2024-43883 is a race condition vulnerability in the Linux kernel's USB vhci-hcd (virtual host controller interface) driver where stale pointer references can remain in use after being released, potentially leading to use-after-free memory access.

Is CVE-2024-43883 being actively exploited?

No, there are currently no reports of active exploitation in the wild, and no public exploit code is available. However, the high CVSS score of 7.0 indicates significant local privilege escalation risk.

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

Linux kernel versions 6.7 through 6.10.4 are vulnerable. Kernel 6.10.5 and later versions contain the fix.

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

Run `uname -r` to obtain your kernel version. If it falls between 6.7 and 6.10.4, your system is vulnerable. Additionally, confirm the vhci-hcd module is loaded with `lsmod | grep vhci_hcd`.

Does Defensia detect CVE-2024-43883?

Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-43883 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-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.
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.
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-38541CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: of: module: add buffer overflow check in of_modalias() In of_modalias(), if the buffer happens to be too small even for the 1st snprintf() call, the len parameter will become negative and str parameter (if not NULL initially) will point beyond the buffer's end. Add the buffer overflow check after the 1st snprintf() call and fix such check after the strlen() call (accounting for the terminating NUL char).

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

Get started free