CVE-2026-43086
NULL Pointer Dereference in Linux Kernel IPVS
Publication date: 2026-05-06
Last updated on: 2026-05-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | From 6.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability can cause a kernel panic in affected Linux systems, leading to a system crash or denial of service. The NULL pointer dereference in the ipvs component can disrupt normal network service operations that rely on IP Virtual Server functionality.
Such a crash can result in downtime, loss of availability, and potential disruption of services running on the affected system.
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's IP Virtual Server (ipvs) component. Specifically, it involves a NULL pointer dereference in the error handling path of the ip_vs_add_service() function.
When ip_vs_bind_scheduler() succeeds, a local variable named sched is set to NULL. If a subsequent call to ip_vs_start_estimator() fails, the cleanup code calls ip_vs_unbind_scheduler() with sched still set to NULL. Although ip_vs_unbind_scheduler() checks if the scheduler is installed via svc->scheduler, it then dereferences the NULL sched pointer, causing a kernel panic due to a NULL pointer dereference.
The fix involves not clearing the sched variable after a successful bind, ensuring that the correct pointer is passed during cleanup and preventing the NULL dereference and kernel panic.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by ensuring that the local variable 'sched' is not cleared after a successful bind in the ip_vs_add_service() function. This prevents a NULL pointer dereference in the error path.
Immediate mitigation steps include updating your Linux kernel to a version that contains this fix, such as kernel version 6.2 or later where the error path handling has been corrected.