CVE-2026-43164
Null Pointer Dereference in Linux Kernel UDPLite
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 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a null pointer dereference in the Linux kernel's udplite implementation, specifically in the function __udp_enqueue_schedule_skb().
The issue occurs because udp_sk(sk)->udp_prod_queue can be null, leading to a null pointer dereference when accessed.
This was reported by syzbot and involves failure scenarios in socket initialization functions like udp_lib_init_sock(), udp_init_sock(), and udpv6_init_sock().
The fix involves handling errors properly in udplite_sk_init() and udplitev6_sk_init() to prevent the null pointer dereference.
How can this vulnerability impact me? :
A null pointer dereference in the kernel can cause a system crash or kernel panic, leading to denial of service.
This means that an attacker or a faulty process could potentially cause the affected Linux system to become unstable or unresponsive.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a null pointer dereference in the Linux kernel's udplite implementation, specifically in the __udp_enqueue_schedule_skb() function. Detection would typically involve monitoring kernel logs for crash reports or BUG messages related to null pointer dereferences in UDP or udplite code paths.
You can check your system logs for kernel BUG messages or KASAN reports indicating null pointer dereferences related to udp_sk or udplite. For example, use the following command to search kernel logs:
- dmesg | grep -i 'null-ptr-deref'
- journalctl -k | grep -i 'udp_enqueue_schedule_skb'
Additionally, monitoring for kernel crashes or oops messages related to UDP or udplite sockets can help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by fixing the null pointer dereference in the Linux kernel's udplite code. Immediate mitigation steps include updating your Linux kernel to a version that contains the fix for this issue.
If updating the kernel is not immediately possible, consider disabling or restricting the use of udplite sockets if feasible in your environment to reduce exposure.
Monitoring system logs for signs of exploitation attempts and applying any vendor-provided patches or advisories related to this vulnerability is also recommended.