CVE-2024-47730
📋 TL;DR
A use-after-free vulnerability in the Linux kernel's HiSilicon QM crypto accelerator driver could allow attackers to cause memory corruption or potentially execute arbitrary code. This affects systems using HiSilicon hardware acceleration with vulnerable kernel versions. Attackers need local access to exploit this vulnerability.
💻 Affected Systems
- Linux kernel with HiSilicon QM crypto accelerator driver
📦 What is this software?
Linux Kernel by Linux
The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...
Learn more about Linux Kernel →Linux Kernel by Linux
The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...
Learn more about Linux Kernel →Linux Kernel by Linux
The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...
Learn more about Linux Kernel →Linux Kernel by Linux
The Linux Kernel is the core component of the Linux operating system, serving as the critical interface between computer hardware and software processes. As the heart of millions of servers, cloud infrastructure, embedded systems, Android devices, and IoT deployments worldwide, the Linux Kernel mana...
Learn more about Linux Kernel →⚠️ Risk & Real-World Impact
Worst Case
Local privilege escalation to kernel-level execution, potentially leading to full system compromise, data theft, or persistent backdoor installation.
Likely Case
Kernel panic leading to denial of service (system crash) or memory corruption causing system instability.
If Mitigated
Limited to denial of service if proper kernel hardening and access controls prevent privilege escalation.
🎯 Exploit Status
Exploitation requires local access and knowledge of memory layout. No public exploits known at this time.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Kernel versions containing commits: 801d64177faaec184cee1e1aa4d8487df1364a54, 85e81103033324d7a271dafb584991da39554a89, 98d3be34c9153eceadb56de50d9f9347e88d86e4, aa3e0db35a60002fb34ef0e4ad203aa59fd00203, b04f06fc0243600665b3b50253869533b7938468
Vendor Advisory: https://git.kernel.org/stable/c/801d64177faaec184cee1e1aa4d8487df1364a54
Restart Required: Yes
Instructions:
1. Update to a patched kernel version from your distribution. 2. Reboot the system to load the new kernel. 3. Verify the fix is applied by checking kernel version or commit hash.
🔧 Temporary Workarounds
Disable HiSilicon QM accelerator
linuxTemporarily disable the vulnerable driver module if not required
sudo modprobe -r hisi_qm
echo 'blacklist hisi_qm' | sudo tee /etc/modprobe.d/blacklist-hisi_qm.conf
🧯 If You Can't Patch
- Restrict local access to systems using strict user permissions and access controls
- Implement kernel hardening measures like SELinux/AppArmor to limit impact of potential exploitation
🔍 How to Verify
Check if Vulnerable:
Check if the hisi_qm module is loaded: lsmod | grep hisi_qm. If loaded and kernel version is unpatched, system is vulnerable.
Check Version:
uname -r
Verify Fix Applied:
Check kernel version against patched versions from your distribution, or verify the fix commit is present in kernel source.
📡 Detection & Monitoring
Log Indicators:
- Kernel oops messages related to hisi_qm driver
- System crashes or unexpected reboots
- dmesg errors mentioning memory corruption or use-after-free
Network Indicators:
- None - this is a local vulnerability
SIEM Query:
Search for kernel panic events or module loading errors related to hisi_qm in system logs
🔗 References
- https://git.kernel.org/stable/c/801d64177faaec184cee1e1aa4d8487df1364a54
- https://git.kernel.org/stable/c/85e81103033324d7a271dafb584991da39554a89
- https://git.kernel.org/stable/c/98d3be34c9153eceadb56de50d9f9347e88d86e4
- https://git.kernel.org/stable/c/aa3e0db35a60002fb34ef0e4ad203aa59fd00203
- https://git.kernel.org/stable/c/b04f06fc0243600665b3b50253869533b7938468
- https://git.kernel.org/stable/c/c5f5b813e546f7fe133539c3d7a5086cc8dd2aa1
- https://git.kernel.org/stable/c/f8024f12752e32ffbbf59e1c09d949f977ff743f
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html