CVE-2022-49419

7.8 HIGH

📋 TL;DR

A use-after-free vulnerability in the Linux kernel's vesafb video framebuffer driver allows local attackers to potentially crash the system or execute arbitrary code. This affects Linux systems with vesafb enabled, requiring local access to exploit. The vulnerability occurs when the driver improperly handles memory cleanup during device removal.

💻 Affected Systems

Products:
  • Linux kernel
Versions: Versions before the fix commits (specific versions vary by distribution)
Operating Systems: Linux distributions using affected kernel versions
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with vesafb framebuffer driver loaded. Many modern systems use other framebuffer drivers.

📦 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 →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local privilege escalation to kernel-level code execution, potentially leading to full system compromise.

🟠

Likely Case

Kernel panic or system crash causing denial of service.

🟢

If Mitigated

No impact if vesafb driver is not loaded or system is patched.

🌐 Internet-Facing: LOW - Requires local access to exploit, not remotely exploitable.
🏢 Internal Only: MEDIUM - Local attackers with user access could exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires local access and knowledge of kernel memory layout. No public exploits known.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Kernel versions containing commits: 0fac5f8fb1bc2fc4f8714bf5e743c9cc3f547c63, acde4003efc16480375543638484d8f13f2e99a3, d260cad015945d1f4bb9b028a096f648506106a2, f605f5558ecc175ec70016a3c15f007cb6386531

Vendor Advisory: https://git.kernel.org/stable/c/0fac5f8fb1bc2fc4f8714bf5e743c9cc3f547c63

Restart Required: Yes

Instructions:

1. Update Linux kernel to patched version from your distribution's repositories. 2. Reboot system to load new kernel.

🔧 Temporary Workarounds

Disable vesafb module

Linux

Prevent loading of vulnerable vesafb driver

echo 'blacklist vesafb' >> /etc/modprobe.d/blacklist.conf
update-initramfs -u

🧯 If You Can't Patch

  • Restrict local user access to prevent exploitation
  • Monitor system logs for kernel panics or crashes

🔍 How to Verify

Check if Vulnerable:

Check if vesafb module is loaded: lsmod | grep vesafb AND check kernel version against patched versions

Check Version:

uname -r

Verify Fix Applied:

Verify kernel version includes fix commits and vesafb module loads without issues

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic messages
  • Use-after-free kernel oops in dmesg
  • System crashes related to framebuffer

Network Indicators:

  • None - local exploit only

SIEM Query:

source="kernel" AND ("panic" OR "oops" OR "use-after-free") AND "vesafb"

🔗 References

📤 Share & Export