Vulnerability · Published Jan 23, 2026 · Assigned by Linux

CVE-2026-22983net: do not write to msg_get_inq in callee

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: net: do not write to msg_get_inq in callee NULL pointer dereference fix. msg_get_inq is an input field from caller to callee. Don't set it in the callee, as the caller may not clear it on struct reuse. This is a kernel-internal variant of msghdr only, and the only user does reinitialize the field. So this is not critical for that reason. But it is more robust to avoid the write, and slightly simpler code. And it fixes a bug, see below. Callers set msg_get_inq to request the input queue length to be returned in msg_inq. This is equivalent to but independent from the SO_INQ request to return that same info as a cmsg (tp->recvmsg_inq). To reduce branching in the hot path the second also sets the msg_inq. That is WAI. This is a fix to commit 4d1442979e4a ("af_unix: don't post cmsg for SO_INQ unless explicitly asked for"), which fixed the inverse. Also avoid NULL pointer dereference in unix_stream_read_generic if state->msg is NULL and msg->msg_get_inq is written. A NULL state->msg can happen when splicing as of commit 2b514574f7e8 ("net: af_unix: implement splice for stream af_unix sockets"). Also collapse two branches using a bitwise or.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux6.18.8-1DEBIAN-CVE-2026-22983
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-22983
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-22983

Affected products (as reported)

VendorProductVersions
Linux Linux 089e50f29eeec8eef6ae1450fc88138d719291cb – before ffa2be496ef65055b28b39c6bd9a7d66943ee89a4d1442979e4a53b9457ce1e373e187e1511ff688 – before 7d11e047eda5f98514ae62507065ac961981c025
Linux Linux 6.18.4 – before 6.18.6

References