CVE-2024-36896·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix access violation during port device removal Testing with KASAN and syzkaller revealed a bug in port.c:disable_store(): usb_hub_to_struct_hub() can return NULL if the hub that the port belongs to is concurrently removed, but the function does not check for this possibility before dereferencing the returned value. It turns out that the first dereference is unnecessary, since hub->intfdev is the parent of the port device, so it can be changed easily. Adding a check for hub == NULL prevents further problems. The same bug exists in the disable_show() routine, and it can be fixed the same way.
- Severity
- critical
- Software
- Kernel
- Fixed in
- 6.8.10
- Published
- 2024-05-30
Affected versions
From: 6.7
Until: 6.8.10
Fixed in: 6.8.10
How to fix this CVE
Update your Linux kernel to version 6.8.10 or later to patch a critical NULL pointer dereference vulnerability in USB port device handling. This vulnerability can be triggered during concurrent USB hub removal operations, leading to kernel crashes or potential privilege escalation. Apply the patch immediately to systems running kernels 6.7 through 6.8.9.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Check kernel version: uname -r — verify it is below 6.8.10; if between 6.7 and 6.8.9, the system is vulnerable
- Confirm USB subsystem is active: lsmod | grep usbcore — if loaded, the vulnerable code path is present
- Search kernel logs for crashes: dmesg | grep -E 'NULL|oops|BUG' — look for USB hub removal related panics
- After patching, verify fix: uname -r should show 6.8.10 or later; reboot if needed and re-run step 1
FAQ
What is CVE-2024-36896?
This CVE describes a null pointer dereference in the Linux kernel's USB port management code. When a USB hub is removed while port operations are ongoing, the kernel fails to validate a pointer before dereferencing it, causing a kernel panic or potential code execution.
Is CVE-2024-36896 being actively exploited?
No, there are no reports of active exploitation in the wild, and no public exploits are currently available. However, the critical CVSS score (9.1) and ease of triggering warrant immediate patching.
What versions of Kernel are affected by CVE-2024-36896?
Linux kernel versions 6.7 through 6.8.9 are vulnerable. Kernel 6.8.10 and later include the fix.
How do I check if my server is vulnerable to CVE-2024-36896?
Run 'uname -r' and check if the version falls between 6.7.0 and 6.8.9; if so, your system is vulnerable and requires immediate kernel update and reboot.
Does Defensia detect CVE-2024-36896?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-36896 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/5f1d68ef5ddac27c6b997adccd1c339cef1e6848
- https://git.kernel.org/stable/c/6119ef6517ce501fc548154691abdaf1f954a277
- https://git.kernel.org/stable/c/63533549ff53d24daf47c443dbd43c308afc3434
- https://git.kernel.org/stable/c/a4b46d450c49f32e9d4247b421e58083fde304ce
- https://git.kernel.org/stable/c/5f1d68ef5ddac27c6b997adccd1c339cef1e6848
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-36896. Free for 1 server.
Get started free