CVE-2021-42252
📋 TL;DR
A memory corruption vulnerability in the Aspeed LPC control driver in Linux kernel allows local attackers to overwrite kernel memory and potentially escalate privileges. The issue occurs due to incorrect size comparisons in the aspeed_lpc_ctrl_mmap function. This affects systems with Aspeed hardware running vulnerable Linux kernel versions.
💻 Affected Systems
- Linux kernel
📦 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 →⚠️ Risk & Real-World Impact
Worst Case
Local privilege escalation to root, enabling complete system compromise, data theft, and persistence establishment.
Likely Case
Local privilege escalation allowing attackers to bypass security controls and execute arbitrary code with kernel privileges.
If Mitigated
Limited impact if proper access controls restrict local user access and SELinux/AppArmor policies are enforced.
🎯 Exploit Status
Requires local access and knowledge of Aspeed LPC interface. No public exploits known as of analysis.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Linux kernel 5.14.6 and later
Vendor Advisory: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.14.6
Restart Required: Yes
Instructions:
1. Update kernel to version 5.14.6 or later. 2. For distributions: Use package manager (apt/yum/dnf) to update kernel package. 3. Reboot system to load new kernel.
🔧 Temporary Workarounds
Disable Aspeed LPC control module
linuxPrevent loading of vulnerable kernel module
echo 'blacklist aspeed-lpc-ctrl' >> /etc/modprobe.d/blacklist.conf
rmmod aspeed_lpc_ctrl
Restrict device access
linuxChange permissions on LPC control device to prevent user access
chmod 600 /dev/aspeed-lpc-ctrl
chown root:root /dev/aspeed-lpc-ctrl
🧯 If You Can't Patch
- Implement strict access controls to limit local user privileges
- Use SELinux/AppArmor to restrict kernel module interactions
🔍 How to Verify
Check if Vulnerable:
Check kernel version: uname -r. If version is earlier than 5.14.6 and Aspeed hardware is present, system is vulnerable.
Check Version:
uname -r
Verify Fix Applied:
Verify kernel version is 5.14.6 or later with uname -r, and check that Aspeed LPC module is either updated or disabled.
📡 Detection & Monitoring
Log Indicators:
- Kernel logs showing memory corruption errors
- Failed privilege escalation attempts in audit logs
- Unexpected kernel module loading
Network Indicators:
- None - local-only vulnerability
SIEM Query:
source="kernel" AND ("aspeed" OR "lpc" OR "memory corruption")
🔗 References
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.14.6
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b49a0e69a7b1a68c8d3f64097d06dabb770fec96
- https://security.netapp.com/advisory/ntap-20211112-0006/
- https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.14.6
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b49a0e69a7b1a68c8d3f64097d06dabb770fec96
- https://security.netapp.com/advisory/ntap-20211112-0006/