CVE-2026-43413
NULL pointer dereference in Linux kernel hisi_sas 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 |
|---|---|---|
| linux | linux_kernel | 7.0.0-rc2+ |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's hisi_sas driver related to SCSI device scanning. The issue occurs because the hisi_sas driver supports only one channel, but the scanning function attempts to scan multiple channels based on a max_channel value of 1. When the scanning function tries to scan channel 1, it triggers a NULL pointer exception, causing a kernel crash or 'Oops' error.
Specifically, the user_scan() function calls sas_user_scan() for channel 0 successfully, but then tries to scan channel 1, which is unsupported by hisi_sas. This leads to a NULL pointer dereference and a kernel panic.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or become unstable due to a NULL pointer dereference when scanning SCSI devices using the hisi_sas driver. This can lead to system downtime, loss of availability, and potential disruption of services running on affected systems.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel NULL pointer dereference error related to the hisi_sas driver during user_scan operations. Detection can be done by monitoring the system kernel logs for specific error messages indicating a NULL pointer exception in the hisi_sas module.
- Check kernel logs for messages similar to: "Unable to handle kernel NULL pointer dereference at virtual address 00000000000008b0" and traces involving sas_user_scan or hisi_sas.
- Use the command: dmesg | grep -i 'hisi_sas' to filter relevant kernel messages.
- Alternatively, monitor for kernel oops or panic messages related to scsi or sas subsystems using: journalctl -k | grep -i 'sas_user_scan' or journalctl -k | grep -i 'NULL pointer dereference'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue arises from a NULL pointer dereference in the hisi_sas driver during multi-channel scans.
Since hisi_sas supports only one channel, avoiding user_scan operations that trigger scans on non-existent channels (channel 1 and above) can help prevent the crash until a patch is applied.
If updating the kernel is not immediately possible, consider disabling or unloading the hisi_sas module temporarily to avoid triggering the vulnerability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not include any details about the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.