CVE-2026-22983
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-02-26
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 | From 6.18.4 (inc) to 6.18.6 (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 involves a NULL pointer dereference in the Linux kernel's networking code. Specifically, the issue arises because the callee function writes to the msg_get_inq field, which is intended as an input from the caller and should not be modified by the callee. If the callee writes to this field when the caller has not properly cleared it, or when the state->msg pointer is NULL (such as during splicing operations), it can cause a NULL pointer dereference, leading to a kernel crash or instability. The fix prevents the callee from writing to msg_get_inq and avoids dereferencing NULL pointers in unix_stream_read_generic.
How can this vulnerability impact me? :
This vulnerability can cause a NULL pointer dereference in the Linux kernel, which may lead to kernel crashes or system instability. While it is not considered critical because the only user reinitializes the field, exploitation could result in denial of service or unexpected behavior in systems using affected kernel versions.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in the Linux kernel by avoiding writing to the msg_get_inq field in the callee to prevent NULL pointer dereference. To mitigate this vulnerability, you should update your Linux kernel to a version that includes this fix (post commit 4d1442979e4a and 2b514574f7e8).