CVE-2026-43294
Kernel Panic on Reboot in RZ/G2L MIPI-DSI Driver
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| renesas | rz-du | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by updating the Linux kernel to include the patch that moves the rzg2l_mipi_dsi_stop() call to the new callback function rzg2l_mipi_dsi_atomic_post_disable().
Immediate mitigation steps include:
- Update your Linux kernel to a version that contains the fix for this issue.
- Avoid rebooting the system with affected panels until the fix is applied to prevent kernel panic.
- Monitor system logs for any signs of kernel panic related to this issue and plan maintenance windows to apply the patch.
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel related to the Renesas rz-du drm driver, specifically in the mipi_dsi interface. After a certain commit, some display panels that send MIPI-DSI commands during their unprepare() callback cause a kernel panic when the system reboots.
The issue arises because the MIPI-DSI interface is stopped too early, causing the function rzg2l_mipi_dsi_host_transfer() to trigger a kernel panic during the reboot process.
The fix involved moving the stop function (rzg2l_mipi_dsi_stop()) to a new callback (rzg2l_mipi_dsi_atomic_post_disable()) to ensure the correct power-down and stop sequence, preventing the kernel panic.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic during system reboot on devices using affected Renesas panels with the rz-du driver. This kernel panic can lead to system instability, failed reboots, or crashes, potentially causing downtime or requiring manual intervention to recover the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel panic during system reboot on affected panels using the Renesas rz-du drm driver with MIPI-DSI interface.
To detect this issue on your system, you can monitor the system logs for kernel panic messages related to the drm renesas rz-du driver and MIPI-DSI interface during reboot.
- Check the system log for kernel panic traces with commands like: sudo journalctl -b -1 | grep -i 'kernel panic' or sudo dmesg | grep -i 'rzg2l_mipi_dsi_host_transfer'
- Look for call traces mentioning functions such as rzg2l_mipi_dsi_host_transfer, mipi_dsi_device_transfer, or ili9881c_unprepare during reboot sequences.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information about CVE-2026-43294 does not include any details regarding its impact on compliance with common standards and regulations such as GDPR or HIPAA.