LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-22983 is a Linux kernel bug in internal socket receive handling. A bad write to an input flag could contribute to a NULL pointer dereference in AF_UNIX stream splice paths. The source describes it as not critical, but it is still a kernel correctness issue that should be picked up through normal kernel update processes.

Executive priority

Treat as routine-to-important kernel maintenance, not an emergency based on current evidence. Raise priority if your vendor marks deployed kernels affected or if operational crash evidence appears.

Technical view

The fix stops callee code from writing msg_get_inq, an input field in the kernel-internal msghdr variant. Reused structures and splice handling can leave state->msg NULL, allowing unix_stream_read_generic to hit a NULL pointer dereference when msg_get_inq is written. The referenced stable commits implement the robustness fix.

Likely exposure

Exposure appears limited to Linux kernels containing the affected AF_UNIX changes before the referenced stable fixes. The source bundle does not identify affected distributions, configurations, privileges required, or remotely reachable services.

Exploitation context

No active exploitation is stated. The CVE is not listed as KEV in the bundle, and the provided sources do not describe exploitability, weaponization, or real-world attacks.

Researcher notes

The record gives commit-level context but lacks CVSS, CWE, distribution mapping, exploit preconditions, and impact detail beyond NULL pointer dereference. Avoid assuming remote reachability or privilege requirements without vendor analysis.

Mitigation direction

  • Check Linux vendor advisories for CVE-2026-22983 applicability.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize systems running custom or upstream kernels near the affected commits.
  • If patching is delayed, follow vendor-specific mitigations when published.

Validation and detection

  • Inventory Linux kernel builds across managed systems.
  • Compare installed kernels against vendor errata for CVE-2026-22983.
  • Confirm kernel changelogs include the referenced AF_UNIX msg_get_inq fix.
  • Review kernel crash reports for related AF_UNIX NULL dereference signatures.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-22983 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux089e50f29eeec8eef6ae1450fc88138d719291cb, 4d1442979e4a53b9457ce1e373e187e1511ff688unaffected
LinuxLinux6.18.4unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.