CVE-2026-23000
BaseFortify
Publication date: 2026-01-25
Last updated on: 2026-02-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.12 (inc) to 6.12.67 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.7 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's mlx5e network driver when changing network device profiles. If the function mlx5e_netdev_change_profile fails to attach a new profile and also fails to rollback to the old profile, it can leave a dangling network device with a reset private data structure. Subsequent attempts to change the profile can cause the kernel to crash due to a NULL pointer dereference when accessing invalid memory.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (kernel oops) when retrying to change the network device profile after a failure. This can lead to system instability or downtime, affecting network functionality and potentially causing service interruptions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring kernel logs for specific error messages related to mlx5e_netdev_change_profile failures and crashes when enabling switchdev mode. You can check the kernel log for messages like 'mlx5e_netdev_change_profile: failed to rollback to orig profile' or 'BUG: kernel NULL pointer dereference' related to mlx5e. Commands to check kernel logs include: 'dmesg | grep mlx5e_netdev_change_profile' and 'journalctl -k | grep mlx5e'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version that contains the fix for this vulnerability, which properly handles failures in mlx5e_netdev_change_profile and avoids crashes on profile change rollback failure. Until the update is applied, avoid retrying to enable switchdev mode multiple times on affected devices to prevent kernel crashes.