CVE-2022-50441
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-10-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the net/mlx5 driver where a recent code change accidentally removed a call to cancel delayed bond work. As a result, delayed work tasks may execute on a workqueue that has already been destroyed, leading to kernel crashes such as NULL pointer dereferences and supervisor write access faults. The fix restores the call to cancel_delayed_work_sync() before destroying the workqueue to prevent these crashes.
How can this vulnerability impact me? :
This vulnerability can cause kernel crashes and instability due to NULL pointer dereferences when delayed work is executed on destroyed workqueues. This can lead to system crashes, potential downtime, and loss of service on affected Linux systems using the mlx5 driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel call traces indicating a NULL pointer dereference related to mlx5 delayed bond work. Specifically, look for kernel BUG messages and call traces similar to those shown in the description, such as 'BUG: kernel NULL pointer dereference' and workqueue errors involving mlx5_core. Commands to check the kernel logs include: 'dmesg | grep -i mlx5', 'journalctl -k | grep -i BUG', or 'journalctl -k | grep -i mlx5'.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to update the Linux kernel to a version that includes the fix restoring the call to cancel_delayed_work_sync() before destroying the workqueue in the mlx5 driver. This prevents the delayed bond work from executing on a destroyed workqueue and avoids the kernel NULL pointer dereference. Until the update is applied, monitoring for the described kernel errors and avoiding workloads that trigger mlx5 delayed bond work may reduce risk.