CVE-2026-23173
NULL Pointer Dereference in Linux mlx5e TC Flow Deletion
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 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 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.7 (inc) to 6.12.69 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.9 (exc) |
| linux | linux_kernel | From 6.5 (inc) to 6.6.123 (exc) |
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 exists in the Linux kernel's mlx5e network driver, specifically in the handling of TC (Traffic Control) steering flows. The issue occurs when deleting TC steering flows, where the code incorrectly assumes all possible ports exist instead of iterating only over actual device communication peers. This can lead to attempts to access non-existent peers, causing a kernel NULL pointer dereference and resulting in a kernel crash (Oops).
How can this vulnerability impact me? :
The impact of this vulnerability is a potential kernel crash due to a NULL pointer dereference when deleting TC steering flows in the mlx5e driver. This can cause system instability or denial of service as the kernel encounters an unrecoverable error.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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 causing a kernel oops with messages related to mlx5e_tc_del_fdb_peers_flow and TC steering flows.
To detect this vulnerability on your system, you should monitor kernel logs for oops or panic messages referencing mlx5e_tc_del_fdb_peers_flow or mlx5_core modules.
Commands to check kernel logs include:
- dmesg | grep -i mlx5e_tc_del_fdb_peers_flow
- journalctl -k | grep -i mlx5e_tc_del_fdb_peers_flow
- grep -i 'BUG: kernel NULL pointer dereference' /var/log/kern.log
Additionally, monitoring for crashes or errors related to the 'tc' command or traffic control flows involving mlx5e devices may help identify attempts to trigger this issue.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by ensuring that TC steering flows are deleted only for existing device communication peers, avoiding touching non-existent peers.
Immediate mitigation steps include:
- Update the Linux kernel to a version that includes the fix for this vulnerability.
- Avoid using TC steering flows or deleting flows on mlx5e devices until the kernel is patched.
- Monitor kernel logs for related errors and avoid running untrusted traffic control commands that may trigger the issue.