{ "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-23413", "tracking": { "current_release_date": "2026-04-03T07:03:48.001547Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-23413", "initial_release_date": "2026-04-02T12:27:32.291136Z", "revision_history": [ { "date": "2026-04-02T12:27:32.291136Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| References created (5)." }, { "date": "2026-04-02T12:27:37.441404Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-04-02T12:38:49.329490Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| Products created (6).| Products connected (7).| References created (5)." }, { "date": "2026-04-02T12:38:59.958153Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-04-02T15:22:27.433553Z", "number": "5", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-04-02T15:22:36.693249Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-04-02T18:44:51.649443Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Products connected (2)." }, { "date": "2026-04-03T00:27:41.952957Z", "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-04-03T00:27:46.035293Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-04-03T06:43:54.145777Z", "number": "10", "summary": "Description created for source." } ], "status": "interim", "version": "10" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<0509b762bc5e8ea7b8391130730c6d8502fc6e69", "product": { "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<0509b762bc5e8ea7b8391130730c6d8502fc6e69", "product_id": "CSAFPID-5984722" } }, { "category": "product_version_range", "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<37bef86e5428d59f70a4da82b80f9a8f252fecbe", "product": { "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<37bef86e5428d59f70a4da82b80f9a8f252fecbe", "product_id": "CSAFPID-5984720" } }, { "category": "product_version_range", "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<4c9af67f99aa3e51b522c54968ab3ac8272be41c", "product": { "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|<4c9af67f99aa3e51b522c54968ab3ac8272be41c", "product_id": "CSAFPID-5984721" } }, { "category": "product_version_range", "name": "vers:git/1cb6f0bae50441f4b4b32a28315853b279c7404e|ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-23413" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved:\n\nclsact: Fix use-after-free in init/destroy rollback asymmetry\n\nFix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry.\nThe latter is achieved by first fully initializing a clsact instance, and\nthen in a second step having a replacement failure for the new clsact qdisc\ninstance. clsact_init() initializes ingress first and then takes care of the\negress part. This can fail midway, for example, via tcf_block_get_ext(). Upon\nfailure, the kernel will trigger the clsact_destroy() callback.\n\nCommit 1cb6f0bae504 (\"bpf: Fix too early release of tcx_entry\") details the\nway how the transition is happening. If tcf_block_get_ext on the q->ingress_block\nends up failing, we took the tcx_miniq_inc reference count on the ingress\nside, but not yet on the egress side. clsact_destroy() tests whether the\n{ingress,egress}_entry was non-NULL. However, even in midway failure on the\nreplacement, both are in fact non-NULL with a valid egress_entry from the\nprevious clsact instance.\n\nWhat we really need to test for is whether the qdisc instance-specific ingress\nor egress side previously got initialized. This adds a small helper for checking\nthe miniq initialization called mini_qdisc_pair_inited, and utilizes that upon\nclsact_destroy() in order to fix the use-after-free scenario. Convert the\ningress_destroy() side as well so both are consistent to each other.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23413.json" }, { "category": "description", "text": "A flaw was found in the Linux kernel's clsact qdisc. This use-after-free vulnerability occurs due to an asymmetry in the initialization and destruction rollback process. When a replacement clsact qdisc instance fails during initialization, the destroy callback is triggered without properly de-initializing the ingress or egress sides, leading to the reuse of freed memory. This can result in system instability or a denial of service.", "title": "redhat - https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23413.json" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved: clsact: Fix use-after-free in init/destroy rollback asymmetry Fix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry. The latter is achieved by first fully initializing a clsact instance, and then in a second step having a replacement failure for the new clsact qdisc instance. clsact_init() initializes ingress first and then takes care of the egress part. This can fail midway, for example, via tcf_block_get_ext(). Upon failure, the kernel will trigger the clsact_destroy() callback. Commit 1cb6f0bae504 (\"bpf: Fix too early release of tcx_entry\") details the way how the transition is happening. If tcf_block_get_ext on the q->ingress_block ends up failing, we took the tcx_miniq_inc reference count on the ingress side, but not yet on the egress side. clsact_destroy() tests whether the {ingress,egress}_entry was non-NULL. However, even in midway failure on the replacement, both are in fact non-NULL with a valid egress_entry from the previous clsact instance. What we really need to test for is whether the qdisc instance-specific ingress or egress side previously got initialized. This adds a small helper for checking the miniq initialization called mini_qdisc_pair_inited, and utilizes that upon clsact_destroy() in order to fix the use-after-free scenario. Convert the ingress_destroy() side as well so both are consistent to each other.", "title": "debian - https://security-tracker.debian.org/tracker/CVE-2026-23413" }, { "category": "other", "text": "0.00018", "title": "EPSS" }, { "category": "other", "text": "4.4", "title": "NCSC Score" }, { "category": "other", "text": "Is related to an uncommon cwe id", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "Is related to a product by vendor Linux", "title": "NCSC Score top decreasing factors" }, { "category": "details", "text": "Severity: 2\n", "title": "Vendor assessment" } ], "product_status": { "known_affected": [ "CSAFPID-1286298", "CSAFPID-5984719", "CSAFPID-5984720", "CSAFPID-5984721", "CSAFPID-5984722", "CSAFPID-5984723", "CSAFPID-5984724", "CSAFPID-1439319", "CSAFPID-1439321", "CSAFPID-1453376", "CSAFPID-1453381", "CSAFPID-1453382", "CSAFPID-2858634", "CSAFPID-2858635" ], "known_not_affected": [ "CSAFPID-1286299", "CSAFPID-5904647", "CSAFPID-5904671", "CSAFPID-5905005", "CSAFPID-5905006", "CSAFPID-5905027", "CSAFPID-2036022", "CSAFPID-2036023", "CSAFPID-1439315", "CSAFPID-1439317", "CSAFPID-1453377", "CSAFPID-1453378", "CSAFPID-1453379", "CSAFPID-1453380" ] }, "references": [ { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-23413" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23413.json" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - debian", "url": "https://security-tracker.debian.org/tracker/CVE-2026-23413" }, { "category": "external", "summary": "Source - redhat", "url": "https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23413.json" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/0509b762bc5e8ea7b8391130730c6d8502fc6e69" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/37bef86e5428d59f70a4da82b80f9a8f252fecbe" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/4c9af67f99aa3e51b522c54968ab3ac8272be41c" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/a0671125d4f55e1e98d9bde8a0b671941987e208" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/a73d95b57bf9faebdfed591bcb7ed9292062a84c" }, { "category": "external", "summary": "Reference - redhat", "url": "https://www.cve.org/CVERecord?id=CVE-2026-23413" }, { "category": "external", "summary": "Reference - redhat", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23413" }, { "category": "external", "summary": "Reference - redhat", "url": "https://lore.kernel.org/linux-cve-announce/2026040203-CVE-2026-23413-fa13@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-1439319", "CSAFPID-1439321", "CSAFPID-1453376", "CSAFPID-1453381", "CSAFPID-1453382", "CSAFPID-2858634", "CSAFPID-2858635", "CSAFPID-5984719", "CSAFPID-5984720", "CSAFPID-5984721", "CSAFPID-5984722", "CSAFPID-5984723", "CSAFPID-5984724" ] } ], "title": "CVE-2026-23413" } ] }