CVE-2024-27433·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: clk: mediatek: mt7622-apmixedsys: Fix an error handling path in clk_mt8135_apmixed_probe() 'clk_data' is allocated with mtk_devm_alloc_clk_data(). So calling mtk_free_clk_data() explicitly in the remove function would lead to a double-free. Remove the redundant call.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.8.2
- Published
- 2024-05-17
Affected versions
From: 6.8
Until: 6.8.2
Fixed in: 6.8.2
How to fix this CVE
Update your Linux kernel to version 6.8.2 or later to resolve a memory management defect in the MediaTek clock driver initialization code. The vulnerability stems from improper cleanup logic that could trigger a double-free condition during driver probe operations. Systems running kernel versions 6.8 through 6.8.1 should prioritize this update.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Run 'uname -r' to check your current kernel version. Versions 6.8.0 and 6.8.1 are vulnerable.
- Step 2: Verify if MediaTek clock components are loaded by running 'lsmod | grep -i clk' and check for mt7622 or mt8135 related modules.
- Step 3: Search kernel logs for clk probe failures: 'sudo dmesg | grep -i "apmixed\|clk.*error"' or check '/var/log/kern.log' for unresolved memory issues during boot.
- Step 4: After updating to 6.8.2+, confirm with 'uname -r' and verify no clock-related errors in 'sudo journalctl -k' output.
FAQ
What is CVE-2024-27433?
A memory safety flaw in the Linux kernel's MediaTek clock driver probe function that causes a double-free when the devm-managed clock data structure is deallocated both implicitly and explicitly. This can lead to kernel crashes or undefined behavior.
Is CVE-2024-27433 being actively exploited?
No, there are no known active exploits in the wild and CISA has not listed this vulnerability in their Known Exploited Vulnerabilities catalog.
What versions of Kernel are affected by CVE-2024-27433?
Linux kernel versions 6.8.0 and 6.8.1 are affected. The fix is included in kernel 6.8.2 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2024-27433?
Run 'uname -r' and compare the output. If it shows 6.8.0 or 6.8.1, your system is vulnerable. If it shows 6.8.2 or higher, you are patched.
Does Defensia detect CVE-2024-27433?
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-27433 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/a32e88f2b20259f5fe4f8eed598bbc85dc4879ed
- https://git.kernel.org/stable/c/de3340533bd68a7b3d6be1841b8eb3fa6c762fe6
- https://git.kernel.org/stable/c/f3633fed984f1db106ff737a0bb52fadb2d89ac7
- https://git.kernel.org/stable/c/fa761ce7a1d15cca1a306b3635f81a22b15fee5b
- https://git.kernel.org/stable/c/a32e88f2b20259f5fe4f8eed598bbc85dc4879ed
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-27433. Free for 1 server.
Get started free