CVE-2025-21688 in Linux
Sumário
de VulDB • 20/05/2026
Based on the kernel log snippet provided, here is an analysis of the issue:
### **Summary** You are experiencing a **kernel crash (Oops/Panic)** in the **V3D GPU driver** (`v3d`) on a **Raspberry Pi 5**. The crash occurs in the interrupt handler (`v3d_irq`) while the `chromium` browser was running.
---
### **Key Details from the Log** 1. **Hardware**: Raspberry Pi 5 Model B Rev 1.0 2. **Kernel**: `6.13.0-v8+` (This is a very recent, likely mainline or near-mainline kernel) 3. **Process**: `chromium` (PID 2008) 4. **Faulting Function**: `v3d_irq+0x118/0x2e0 [v3d]`
- This is the interrupt handler for the V3D GPU. - The crash happened while handling a GPU interrupt. 5. **Tainted**: `[C]=CRAP`
- This means the kernel was loaded with a non-GPL module or proprietary code, but in the context of Raspberry Pi, this is often just a standard taint flag and not necessarily the cause of the crash.
---
### **Likely Causes** 1. **GPU Driver Bug**: The V3D driver in kernel `6.13` may have a bug in its interrupt handling path, especially under load from Chromium (which uses GPU acceleration). 2. **Hardware Issue**: Rare, but possible GPU or memory corruption. 3. **Outdated Firmware/Kernel**: The `6.13.0-v8+` kernel might be a development or early-release kernel with known issues.
---
### **Recommended Actions**
#### **1. Update Kernel and Firmware** - Ensure you are on the **latest stable kernel**. Kernel `6.13` is very new, and bugs are common. ```bash sudo apt update sudo apt full-upgrade sudo rpi-update # Only if you are comfortable with testing kernels ``` - Check if a newer kernel (e.g., `6.1.x` stable or `6.14+`) has fixed this issue.
#### **2. Disable GPU Acceleration in Chromium** - As a workaround, disable hardware acceleration in Chromium: - Go to `chrome://settings/system` - Turn off **"Use hardware acceleration when available"** - Restart Chromium.
#### **3. Check for Known Issues** - Search the [Raspberry Pi Forums](https://forums.raspberrypi.com/) or [GitHub issues](https://github.com/raspberrypi/linux/issues) for "v3d_irq crash chromium" or "Raspberry Pi 5 kernel 6.13 v3d".
- Look for patches or workarounds in recent commits.
#### **4. Collect More Debug Info** - Enable kernel debugging if possible: ```bash sudo dmesg -w ``` - Check if the crash is reproducible with other GPU-intensive apps (e.g., `glxgears`, `mpv`).
#### **5. Report the Bug** - If the issue persists, report it to the Raspberry Pi kernel maintainers with: - Full `dmesg` output - Kernel version (`uname -r`) - Steps to reproduce
---
### **Temporary Workaround** If you need immediate stability: 1. **Downgrade to a stable kernel** (e.g., `6.1.x` LTS if available). 2. **Disable GPU acceleration** in Chromium. 3. **Monitor temperatures** (`vcgencmd measure_temp`) to rule out thermal throttling causing instability.
Let me know if you need help with any of these steps!
If you want to get best quality of vulnerability data, you may have to visit VulDB.