net: microchip: sparx5: Fix potential null-ptr-deref in sparx_stats_init() and sparx5_start()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.806.0.106.1In the Linux kernel, the following vulnerability has been resolved:
net: microchip: sparx5: Fix potential null-ptr-deref in sparx_stats_init() and sparx5_start()
sparx_stats_init() calls create_singlethread_workqueue() and not checked the ret value, which may return NULL. And a null-ptr-deref may happen:
sparx_stats_init() create_singlethread_workqueue() # failed, sparx5->stats_queue is NULL queue_delayed_work() queue_delayed_work_on() __queue_delayed_work() # warning here, but continue __queue_work() # access wq->flags, null-ptr-deref
Check the ret value and return -ENOMEM if it is NULL. So as sparx5_start().
From the CVE record · Linux
The Linux kernel’s Microchip Sparx5 network driver can dereference a null pointer if workqueue creation fails during initialization or startup. This can cause a crash; the input does not specify an attack path, authentication requirement, or user interaction.
Engineers running Linux kernels with the Microchip Sparx5 network driver should check their versions; affected versions are not specified.