{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-23394", "tracking": { "current_release_date": "2026-03-26T06:45:57.686157Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-23394", "initial_release_date": "2026-03-25T10:41:50.254165Z", "revision_history": [ { "date": "2026-03-25T10:41:50.254165Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| Products created (4).| Products connected (4).| References created (2)." }, { "date": "2026-03-25T10:41:53.322918Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-25T11:33:45.308985Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| References created (2)." }, { "date": "2026-03-25T13:14:56.474106Z", "number": "4", "summary": "Source connected.| CVE status created. (valid)| Products connected (1).| References created (120)." }, { "date": "2026-03-25T13:15:00.016141Z", "number": "5", "summary": "NCSC Score updated." }, { "date": "2026-03-25T18:45:17.298592Z", "number": "6", "summary": "Source created.| CVE status created. (valid)| Products connected (2)." }, { "date": "2026-03-25T18:45:19.565502Z", "number": "7", "summary": "NCSC Score updated." }, { "date": "2026-03-26T00:28:47.118009Z", "number": "8", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (13).| Product Identifiers created (5).| References created (3).| CWES updated (1).| Vendor_assessment created." }, { "date": "2026-03-26T00:28:49.496518Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-03-26T01:10:41.115408Z", "number": "10", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-26T01:10:44.095459Z", "number": "11", "summary": "NCSC Score updated." }, { "date": "2026-03-26T06:45:52.814388Z", "number": "12", "summary": "Description created for source." } ], "status": "interim", "version": "12" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:git/118f457da9ed58a79e24b73c2ef0aa1987241f0e|<37dd7ab332396eb8dd80b2dc7ea4b61abf767436", "product": { "name": "vers:git/118f457da9ed58a79e24b73c2ef0aa1987241f0e|<37dd7ab332396eb8dd80b2dc7ea4b61abf767436", "product_id": "CSAFPID-5905039" } }, { "category": "product_version_range", "name": "vers:git/118f457da9ed58a79e24b73c2ef0aa1987241f0e| true <------.\n \\\n `------ recv(sk-B, MSG_PEEK)\n invalidate !! -> sk-A's file refcount : 1 -> 2\n\n close(sk-B)\n -> sk-B's file refcount : 2 -> 1\n unix_vertex_dead(sk-B)\n -> true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq. GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A. The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23394.json" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved:\n\naf_unix: Give up GC if MSG_PEEK intervened.\n\nIgor Ushakov reported that GC purged the receive queue of\nan alive socket due to a race with MSG_PEEK with a nice repro.\n\nThis is the exact same issue previously fixed by commit\ncbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\").\n\nAfter GC was replaced with the current algorithm, the cited\ncommit removed the locking dance in unix_peek_fds() and\nreintroduced the same issue.\n\nThe problem is that MSG_PEEK bumps a file refcount without\ninteracting with GC.\n\nConsider an SCC containing sk-A and sk-B, where sk-A is\nclose()d but can be recv()ed via sk-B.\n\nThe bad thing happens if sk-A is recv()ed with MSG_PEEK from\nsk-B and sk-B is close()d while GC is checking unix_vertex_dead()\nfor sk-A and sk-B.\n\n GC thread User thread\n --------- -----------\n unix_vertex_dead(sk-A)\n -> true <------.\n \\\n `------ recv(sk-B, MSG_PEEK)\n invalidate !! -> sk-A's file refcount : 1 -> 2\n\n close(sk-B)\n -> sk-B's file refcount : 2 -> 1\n unix_vertex_dead(sk-B)\n -> true\n\nInitially, sk-A's file refcount is 1 by the inflight fd in sk-B\nrecvq. GC thinks sk-A is dead because the file refcount is the\nsame as the number of its inflight fds.\n\nHowever, sk-A's file refcount is bumped silently by MSG_PEEK,\nwhich invalidates the previous evaluation.\n\nAt this moment, sk-B's file refcount is 2; one by the open fd,\nand one by the inflight fd in sk-A. The subsequent close()\nreleases one refcount by the former.\n\nFinally, GC incorrectly concludes that both sk-A and sk-B are dead.\n\nOne option is to restore the locking dance in unix_peek_fds(),\nbut we can resolve this more elegantly thanks to the new algorithm.\n\nThe point is that the issue does not occur without the subsequent\nclose() and we actually do not need to synchronise MSG_PEEK with\nthe dead SCC detection.\n\nWhen the issue occurs, close() and GC touch the same file refcount.\nIf GC sees the refcount being decremented by close(), it can just\ngive up garbage-collecting the SCC.\n\nTherefore, we only need to signal the race during MSG_PEEK with\na proper memory barrier to make it visible to the GC.\n\nLet's use seqcount_t to notify GC when MSG_PEEK occurs and let\nit defer the SCC to the next run.\n\nThis way no locking is needed on the MSG_PEEK side, and we can\navoid imposing a penalty on every MSG_PEEK unnecessarily.\n\nNote that we can retry within unix_scc_dead() if MSG_PEEK is\ndetected, but we do not do so to avoid hung task splat from\nabusive MSG_PEEK calls.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-23394" }, { "category": "description", "text": "A flaw was found in the Linux kernel's af_unix component. A race condition exists between the MSG_PEEK operation and the garbage collection process. This can allow a local user to cause the garbage collector to incorrectly purge the receive queue of an alive socket, potentially leading to a denial of service.\nThis flaw affects AF_UNIX socket file descriptor passing with MSG_PEEK. The race between GC's liveness check and MSG_PEEK refcount bumping can cause GC to incorrectly purge queues of live sockets. This is a regression of a previously fixed issue (commit cbcf01128d0a) that was reintroduced when the GC algorithm was replaced.", "title": "redhat - https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23394.json" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved: af_unix: Give up GC if MSG_PEEK intervened. Igor Ushakov reported that GC purged the receive queue of an alive socket due to a race with MSG_PEEK with a nice repro. This is the exact same issue previously fixed by commit cbcf01128d0a (\"af_unix: fix garbage collect vs MSG_PEEK\"). After GC was replaced with the current algorithm, the cited commit removed the locking dance in unix_peek_fds() and reintroduced the same issue. The problem is that MSG_PEEK bumps a file refcount without interacting with GC. Consider an SCC containing sk-A and sk-B, where sk-A is close()d but can be recv()ed via sk-B. The bad thing happens if sk-A is recv()ed with MSG_PEEK from sk-B and sk-B is close()d while GC is checking unix_vertex_dead() for sk-A and sk-B. GC thread User thread --------- ----------- unix_vertex_dead(sk-A) -> true <------. \\ `------ recv(sk-B, MSG_PEEK) invalidate !! -> sk-A's file refcount : 1 -> 2 close(sk-B) -> sk-B's file refcount : 2 -> 1 unix_vertex_dead(sk-B) -> true Initially, sk-A's file refcount is 1 by the inflight fd in sk-B recvq. GC thinks sk-A is dead because the file refcount is the same as the number of its inflight fds. However, sk-A's file refcount is bumped silently by MSG_PEEK, which invalidates the previous evaluation. At this moment, sk-B's file refcount is 2; one by the open fd, and one by the inflight fd in sk-A. The subsequent close() releases one refcount by the former. Finally, GC incorrectly concludes that both sk-A and sk-B are dead. One option is to restore the locking dance in unix_peek_fds(), but we can resolve this more elegantly thanks to the new algorithm. The point is that the issue does not occur without the subsequent close() and we actually do not need to synchronise MSG_PEEK with the dead SCC detection. When the issue occurs, close() and GC touch the same file refcount. If GC sees the refcount being decremented by close(), it can just give up garbage-collecting the SCC. Therefore, we only need to signal the race during MSG_PEEK with a proper memory barrier to make it visible to the GC. Let's use seqcount_t to notify GC when MSG_PEEK occurs and let it defer the SCC to the next run. This way no locking is needed on the MSG_PEEK side, and we can avoid imposing a penalty on every MSG_PEEK unnecessarily. Note that we can retry within unix_scc_dead() if MSG_PEEK is detected, but we do not do so to avoid hung task splat from abusive MSG_PEEK calls.", "title": "debian - https://security-tracker.debian.org/tracker/CVE-2026-23394" }, { "category": "other", "text": "0.00018", "title": "EPSS" }, { "category": "other", "text": "3.5", "title": "NCSC Score" }, { "category": "other", "text": "Is related to a product by vendor Open Source, Is related to a product by vendor Linux, Is related to a product by vendor Debian, The value of the most recent EPSS score", "title": "NCSC Score top decreasing factors" }, { "category": "details", "text": "Severity: 2\n", "title": "Vendor assessment" } ], "product_status": { "known_affected": [ "CSAFPID-1286298", "CSAFPID-5905039", "CSAFPID-5905040", "CSAFPID-5905041", "CSAFPID-5905042", "CSAFPID-1330297", "CSAFPID-2036024", "CSAFPID-1439321", "CSAFPID-1453376", "CSAFPID-2858634", "CSAFPID-2858635" ], "known_not_affected": [ "CSAFPID-1286299", "CSAFPID-5905006", "CSAFPID-5905027", "CSAFPID-2036023", "CSAFPID-1439315", "CSAFPID-1439317", "CSAFPID-1439319", "CSAFPID-1453377", "CSAFPID-1453378", "CSAFPID-1453379", "CSAFPID-1453380", "CSAFPID-1453381", "CSAFPID-1453382" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23394.json" }, { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-23394" }, { "category": "external", "summary": "Source - certbundde", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-0861.json" }, { "category": "external", "summary": "Source - debian", "url": "https://security-tracker.debian.org/tracker/CVE-2026-23394" }, { "category": "external", "summary": "Source - redhat", "url": "https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23394.json" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/37dd7ab332396eb8dd80b2dc7ea4b61abf767436" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/e5b31d988a41549037b8d8721a3c3cae893d8670" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-0861.json" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-0861" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032522-CVE-2026-23279-cf34@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032523-CVE-2026-23280-cd9e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032523-CVE-2026-23281-2e62@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032523-CVE-2026-23282-bad0@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032523-CVE-2026-23283-3d92@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032523-CVE-2026-23284-ca53@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032524-CVE-2026-23285-ad41@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032524-CVE-2026-23286-8a7e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032524-CVE-2026-23287-93b2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032524-CVE-2026-23288-1d11@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032524-CVE-2026-23289-aa54@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032525-CVE-2026-23290-af97@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032525-CVE-2026-23291-eae3@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032525-CVE-2026-23292-67e8@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032525-CVE-2026-23293-b422@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032525-CVE-2026-23294-1682@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23295-59d2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23296-eb4a@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23297-bcad@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23298-fad9@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23299-6471@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032526-CVE-2026-23300-9bc4@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032527-CVE-2026-23301-09e7@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032527-CVE-2026-23302-e03d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032527-CVE-2026-23303-8e38@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032527-CVE-2026-23304-485b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032527-CVE-2026-23305-5fa4@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032528-CVE-2026-23306-8854@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032528-CVE-2026-23307-60f2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032528-CVE-2026-23308-1e72@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032528-CVE-2026-23309-4243@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032528-CVE-2026-23310-9b67@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032529-CVE-2026-23311-8c0b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032529-CVE-2026-23312-2b11@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032529-CVE-2026-23313-925e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032529-CVE-2026-23314-166c@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032529-CVE-2026-23315-9ac1@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23316-2ce3@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23317-0e9e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23318-bef0@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23319-1e3d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23320-0ae7@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032530-CVE-2026-23321-6059@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032531-CVE-2026-23322-9fd3@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032531-CVE-2026-23323-53db@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032531-CVE-2026-23324-bc9e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032531-CVE-2026-23325-4e3b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032531-CVE-2026-23326-ffc6@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032532-CVE-2026-23327-c497@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032532-CVE-2026-23328-9600@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032532-CVE-2026-23329-c743@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032532-CVE-2026-23330-00fd@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032532-CVE-2026-23331-735b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032533-CVE-2026-23332-50e0@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032533-CVE-2026-23333-417f@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032533-CVE-2026-23334-1b12@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032533-CVE-2026-23335-602d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032533-CVE-2026-23336-d365@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23337-5018@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23338-67c7@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23339-263f@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23340-1aa9@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032534-CVE-2026-23341-3f7b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032535-CVE-2026-23342-8456@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032535-CVE-2026-23343-dc2b@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032535-CVE-2026-23344-0279@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032535-CVE-2026-23345-c154@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032535-CVE-2026-23346-faed@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032536-CVE-2026-23347-fa08@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032536-CVE-2026-23348-e792@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032536-CVE-2026-23349-aa6a@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032536-CVE-2026-23350-f4be@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032536-CVE-2026-23351-637f@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23352-18f2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23353-d0c3@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23354-d9b2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23355-86df@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23356-0014@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032538-CVE-2026-23357-605e@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032538-CVE-2026-23358-1042@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032538-CVE-2026-23359-35fd@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032538-CVE-2026-23360-c464@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032539-CVE-2026-23361-bd5c@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032539-CVE-2026-23362-40bd@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032539-CVE-2026-23363-3e24@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032539-CVE-2026-23364-4267@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032539-CVE-2026-23365-76d3@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032540-CVE-2026-23366-a7c4@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032540-CVE-2026-23367-6e44@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032540-CVE-2026-23368-c240@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032540-CVE-2026-23369-b6c6@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032540-CVE-2026-23370-02d2@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032541-CVE-2026-23371-1b32@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032541-CVE-2026-23372-7bc9@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032541-CVE-2026-23373-0203@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032541-CVE-2026-23374-9345@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032541-CVE-2026-23375-91b1@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032542-CVE-2026-23376-114a@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032542-CVE-2026-23377-cb04@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032542-CVE-2026-23378-f329@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032542-CVE-2026-23379-3b2d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032542-CVE-2026-23380-9e3c@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032543-CVE-2026-23381-378d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032543-CVE-2026-23382-26fe@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032543-CVE-2026-23383-f205@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032543-CVE-2026-23384-489a@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032543-CVE-2026-23385-3414@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032544-CVE-2026-23386-acc4@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032544-CVE-2026-23387-4399@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032544-CVE-2026-23388-9e71@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032544-CVE-2026-23389-2056@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032537-CVE-2026-23390-7146@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032548-CVE-2026-23391-bb43@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032548-CVE-2026-23392-fd9d@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032548-CVE-2026-23393-c395@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032549-CVE-2026-23394-9205@gregkh/" }, { "category": "external", "summary": "Reference - certbundde", "url": "https://lore.kernel.org/linux-cve-announce/2026032549-CVE-2026-23395-5e50@gregkh/" }, { "category": "external", "summary": "Reference - redhat", "url": "https://www.cve.org/CVERecord?id=CVE-2026-23394" }, { "category": "external", "summary": "Reference - redhat", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23394" }, { "category": "external", "summary": "Reference - redhat", "url": "https://lore.kernel.org/linux-cve-announce/2026032549-CVE-2026-23394-9205@gregkh/T" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "baseScore": 5.5, "baseSeverity": "MEDIUM" }, "products": [ "CSAFPID-1286298", "CSAFPID-1330297", "CSAFPID-1439321", "CSAFPID-1453376", "CSAFPID-2036024", "CSAFPID-2858634", "CSAFPID-2858635", "CSAFPID-5905039", "CSAFPID-5905040", "CSAFPID-5905041", "CSAFPID-5905042" ] } ], "title": "CVE-2026-23394" } ] }