CVE-2026-22983

{"id": "CVE-2026-22983", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "affected": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "affectedData": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "089e50f29eeec8eef6ae1450fc88138d719291cb", "lessThan": "ffa2be496ef65055b28b39c6bd9a7d66943ee89a", "versionType": "git"}, {"status": "affected", "version": "4d1442979e4a53b9457ce1e373e187e1511ff688", "lessThan": "7d11e047eda5f98514ae62507065ac961981c025", "versionType": "git"}], "programFiles": ["net/ipv4/tcp.c", "net/unix/af_unix.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.18.4", "lessThan": "6.18.6", "versionType": "semver"}], "programFiles": ["net/ipv4/tcp.c", "net/unix/af_unix.c"], "defaultStatus": "unaffected"}]}], "published": "2026-01-23T16:15:54.333", "references": [{"url": "https://git.kernel.org/stable/c/7d11e047eda5f98514ae62507065ac961981c025", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/ffa2be496ef65055b28b39c6bd9a7d66943ee89a", "tags": ["Patch"], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-476"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: do not write to msg_get_inq in callee\n\nNULL pointer dereference fix.\n\nmsg_get_inq is an input field from caller to callee. Don't set it in\nthe callee, as the caller may not clear it on struct reuse.\n\nThis is a kernel-internal variant of msghdr only, and the only user\ndoes reinitialize the field. So this is not critical for that reason.\nBut it is more robust to avoid the write, and slightly simpler code.\nAnd it fixes a bug, see below.\n\nCallers set msg_get_inq to request the input queue length to be\nreturned in msg_inq. This is equivalent to but independent from the\nSO_INQ request to return that same info as a cmsg (tp->recvmsg_inq).\nTo reduce branching in the hot path the second also sets the msg_inq.\nThat is WAI.\n\nThis is a fix to commit 4d1442979e4a (\"af_unix: don't post cmsg for\nSO_INQ unless explicitly asked for\"), which fixed the inverse.\n\nAlso avoid NULL pointer dereference in unix_stream_read_generic if\nstate->msg is NULL and msg->msg_get_inq is written. A NULL state->msg\ncan happen when splicing as of commit 2b514574f7e8 (\"net: af_unix:\nimplement splice for stream af_unix sockets\").\n\nAlso collapse two branches using a bitwise or."}, {"lang": "es", "value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nnet: no escribir en msg_get_inq en el callee\n\nCorrecci\u00f3n de desreferencia de puntero NULL.\n\nmsg_get_inq es un campo de entrada del caller al callee. No lo establezca en el callee, ya que el caller podr\u00eda no borrarlo al reutilizar la estructura.\n\nEsta es solo una variante interna del kernel de msghdr, y el \u00fanico usuario reinicializa el campo. Por lo tanto, esto no es cr\u00edtico por esa raz\u00f3n. Pero es m\u00e1s robusto evitar la escritura, y un c\u00f3digo ligeramente m\u00e1s simple. Y corrige un error, ver abajo.\n\nLos callers establecen msg_get_inq para solicitar que la longitud de la cola de entrada sea devuelta en msg_inq. Esto es equivalente a, pero independiente de, la solicitud SO_INQ para devolver esa misma informaci\u00f3n como un cmsg (tp->recvmsg_inq). Para reducir las bifurcaciones en la ruta cr\u00edtica, el segundo tambi\u00e9n establece el msg_inq. Eso es WAI.\n\nEsta es una correcci\u00f3n para el commit 4d1442979e4a ('af_unix: no publicar cmsg para SO_INQ a menos que se solicite expl\u00edcitamente'), que corrigi\u00f3 lo inverso.\n\nTambi\u00e9n evitar la desreferencia de puntero NULL en unix_stream_read_generic si state->msg es NULL y se escribe msg->msg_get_inq. Un state->msg NULL puede ocurrir al hacer splicing a partir del commit 2b514574f7e8 ('net: af_unix: implementar splice para sockets af_unix de stream').\n\nTambi\u00e9n colapsar dos ramas usando un OR bit a bit."}], "lastModified": "2026-06-17T10:20:39.030", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "27849DC4-2BBE-4536-8F33-2616A53ACA55", "versionEndExcluding": "6.18.6", "versionStartIncluding": "6.18.4"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "13580667-0A98-40CC-B29F-D12790B91BDB"}], "operator": "OR"}]}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}