CVE-2024-38577·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow There is a possibility of buffer overflow in show_rcu_tasks_trace_gp_kthread() if counters, passed to sprintf() are huge. Counter numbers, needed for this are unrealistically high, but buffer overflow is still possible. Use snprintf() with buffer size instead of sprintf(). Found by Linux Verification Center (linuxtesting.org) with SVACE.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.9.3
- Published
- 2024-06-19
Affected versions
From: 6.9
Until: 6.9.3
Fixed in: 6.9.3
How to fix this CVE
Update your Linux kernel to version 6.9.3 or later to resolve a buffer overflow vulnerability in the RCU tasks trace functionality. This vulnerability affects kernel versions 6.9 through 6.9.2 and could allow local privilege escalation under specific conditions. Apply the kernel update and reboot your system to ensure the fix is active.
sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Check your kernel version: uname -r (vulnerable if output shows 6.9.0, 6.9.1, or 6.9.2)
- Verify the RCU tasks trace component is compiled in: grep CONFIG_TASKS_TRACE_RCU /boot/config-$(uname -r) (if output shows 'y', the component is active)
- Search system logs for memory-related errors: grep -i 'buffer\|overflow\|stack' /var/log/kern.log | head -20
- Confirm the fix by running: uname -r and verifying the version is 6.9.3 or newer after reboot
FAQ
What is CVE-2024-38577?
This is a buffer overflow vulnerability in the Linux kernel's RCU (Read-Copy-Update) tasks trace subsystem that occurs when displaying kernel thread status information. The vulnerability exists in the show_rcu_tasks_trace_gp_kthread() function where sprintf() could write beyond allocated buffer boundaries under certain counter conditions.
Is CVE-2024-38577 being actively exploited?
No, this vulnerability is not currently being actively exploited in the wild. However, it requires local access to trigger and could potentially lead to privilege escalation, so patching is still recommended.
What versions of Kernel are affected by CVE-2024-38577?
Linux kernel versions 6.9 through 6.9.2 are affected. The fix is included in kernel version 6.9.3 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2024-38577?
Run 'uname -r' and check if your kernel version falls within 6.9.0-6.9.2. If it does and CONFIG_TASKS_TRACE_RCU is enabled (grep CONFIG_TASKS_TRACE_RCU /boot/config-$(uname -r)), your system is vulnerable.
Does Defensia detect CVE-2024-38577?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-38577 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/08186d0c5fb64a1cc4b43e009314ee6b173ed222
- https://git.kernel.org/stable/c/17c43211d45f13d1badea3942b76bf16bcc49281
- https://git.kernel.org/stable/c/1a240e138071b25944ded0f5b3e357aa99fabcb7
- https://git.kernel.org/stable/c/32d988f48ed287e676a29a15ac30701c35849aec
- https://git.kernel.org/stable/c/6593d857ce5b5b802fb73d8091ac9c84b92c1697
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-38577. Free for 1 server.
Get started free