{ "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-23417", "tracking": { "current_release_date": "2026-04-03T08:36:12.489681Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-23417", "initial_release_date": "2026-04-02T12:27:53.544281Z", "revision_history": [ { "date": "2026-04-02T12:27:53.544281Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| References created (4)." }, { "date": "2026-04-02T12:28:06.144977Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-04-02T12:38:43.125216Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| Products created (4).| Products connected (6).| References created (4)." }, { "date": "2026-04-02T12:38:47.170186Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-04-02T15:22:26.607568Z", "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:52.893489Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Products connected (2)." }, { "date": "2026-04-03T00:28:34.287224Z", "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:28:37.499460Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-04-03T06:43:51.240397Z", "number": "10", "summary": "Description created for source." } ], "status": "interim", "version": "10" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:git/6082b6c328b5486da2b356eae94b8b83c98b5565|<2321a9596d2260310267622e0ad8fbfa6f95378f", "product": { "name": "vers:git/6082b6c328b5486da2b356eae94b8b83c98b5565|<2321a9596d2260310267622e0ad8fbfa6f95378f", "product_id": "CSAFPID-5984705" } }, { "category": "product_version_range", "name": "vers:git/6082b6c328b5486da2b356eae94b8b83c98b5565|<56af722756ed82fee2ae5d5b4d04743407506195", "product": { "name": "vers:git/6082b6c328b5486da2b356eae94b8b83c98b5565|<56af722756ed82fee2ae5d5b4d04743407506195", "product_id": "CSAFPID-5984702" } }, { "category": "product_version_range", "name": "vers:git/6082b6c328b5486da2b356eae94b8b83c98b5565|= 1.\n\nThe root cause is that convert_ctx_accesses() rewrites BPF_ST|BPF_MEM\nto BPF_ST|BPF_PROBE_MEM32 for arena pointer stores during verification,\nbefore bpf_jit_blind_constants() runs during JIT compilation. The\nblinding switch only matches BPF_ST|BPF_MEM (mode 0x60), not\nBPF_ST|BPF_PROBE_MEM32 (mode 0xa0). The instruction falls through\nunblinded.\n\nAdd BPF_ST|BPF_PROBE_MEM32 cases to bpf_jit_blind_insn() alongside the\nexisting BPF_ST|BPF_MEM cases. The blinding transformation is identical:\nload the blinded immediate into BPF_REG_AX via mov+xor, then convert\nthe immediate store to a register store (BPF_STX).\n\nThe rewritten STX instruction must preserve the BPF_PROBE_MEM32 mode so\nthe architecture JIT emits the correct arena addressing (R12-based on\nx86-64). Cannot use the BPF_STX_MEM() macro here because it hardcodes\nBPF_MEM mode; construct the instruction directly instead.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-23417" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix constant blinding for PROBE_MEM32 stores\n\nBPF_ST | BPF_PROBE_MEM32 immediate stores are not handled by\nbpf_jit_blind_insn(), allowing user-controlled 32-bit immediates to\nsurvive unblinded into JIT-compiled native code when bpf_jit_harden >= 1.\n\nThe root cause is that convert_ctx_accesses() rewrites BPF_ST|BPF_MEM\nto BPF_ST|BPF_PROBE_MEM32 for arena pointer stores during verification,\nbefore bpf_jit_blind_constants() runs during JIT compilation. The\nblinding switch only matches BPF_ST|BPF_MEM (mode 0x60), not\nBPF_ST|BPF_PROBE_MEM32 (mode 0xa0). The instruction falls through\nunblinded.\n\nAdd BPF_ST|BPF_PROBE_MEM32 cases to bpf_jit_blind_insn() alongside the\nexisting BPF_ST|BPF_MEM cases. The blinding transformation is identical:\nload the blinded immediate into BPF_REG_AX via mov+xor, then convert\nthe immediate store to a register store (BPF_STX).\n\nThe rewritten STX instruction must preserve the BPF_PROBE_MEM32 mode so\nthe architecture JIT emits the correct arena addressing (R12-based on\nx86-64). Cannot use the BPF_STX_MEM() macro here because it hardcodes\nBPF_MEM mode; construct the instruction directly instead.", "title": "cveprojectv5 - https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23417.json" }, { "category": "description", "text": "A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) component. This vulnerability occurs because the BPF_ST | BPF_PROBE_MEM32 immediate stores are not correctly handled by the constant blinding mechanism. As a result, user-controlled 32-bit immediate values can remain unblinded in JIT-compiled native code, potentially allowing an attacker to bypass security hardening measures.", "title": "redhat - https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23417.json" }, { "category": "description", "text": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix constant blinding for PROBE_MEM32 stores BPF_ST | BPF_PROBE_MEM32 immediate stores are not handled by bpf_jit_blind_insn(), allowing user-controlled 32-bit immediates to survive unblinded into JIT-compiled native code when bpf_jit_harden >= 1. The root cause is that convert_ctx_accesses() rewrites BPF_ST|BPF_MEM to BPF_ST|BPF_PROBE_MEM32 for arena pointer stores during verification, before bpf_jit_blind_constants() runs during JIT compilation. The blinding switch only matches BPF_ST|BPF_MEM (mode 0x60), not BPF_ST|BPF_PROBE_MEM32 (mode 0xa0). The instruction falls through unblinded. Add BPF_ST|BPF_PROBE_MEM32 cases to bpf_jit_blind_insn() alongside the existing BPF_ST|BPF_MEM cases. The blinding transformation is identical: load the blinded immediate into BPF_REG_AX via mov+xor, then convert the immediate store to a register store (BPF_STX). The rewritten STX instruction must preserve the BPF_PROBE_MEM32 mode so the architecture JIT emits the correct arena addressing (R12-based on x86-64). Cannot use the BPF_STX_MEM() macro here because it hardcodes BPF_MEM mode; construct the instruction directly instead.", "title": "debian - https://security-tracker.debian.org/tracker/CVE-2026-23417" }, { "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: 1\n", "title": "Vendor assessment" } ], "product_status": { "known_affected": [ "CSAFPID-1286675", "CSAFPID-5984702", "CSAFPID-5984703", "CSAFPID-5984704", "CSAFPID-5984705", "CSAFPID-1439319", "CSAFPID-1453381", "CSAFPID-1453382", "CSAFPID-2858634", "CSAFPID-2858635" ], "known_not_affected": [ "CSAFPID-1286676", "CSAFPID-5905027", "CSAFPID-5984161", "CSAFPID-5984170", "CSAFPID-5984171", "CSAFPID-2036022", "CSAFPID-2036023", "CSAFPID-1439315", "CSAFPID-1439317", "CSAFPID-1439321", "CSAFPID-1453376", "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-23417" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/23xxx/CVE-2026-23417.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-23417" }, { "category": "external", "summary": "Source - redhat", "url": "https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-23417.json" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/2321a9596d2260310267622e0ad8fbfa6f95378f" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/56af722756ed82fee2ae5d5b4d04743407506195" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/ccbf29b28b5554f9d65b2fb53b994673ad58b3bf" }, { "category": "external", "summary": "Reference - cveprojectv5; nvd", "url": "https://git.kernel.org/stable/c/de641ea08f8fff6906e169d2576c2ac54e562fbb" }, { "category": "external", "summary": "Reference - redhat", "url": "https://www.cve.org/CVERecord?id=CVE-2026-23417" }, { "category": "external", "summary": "Reference - redhat", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23417" }, { "category": "external", "summary": "Reference - redhat", "url": "https://lore.kernel.org/linux-cve-announce/2026040204-CVE-2026-23417-d6a2@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-1286675", "CSAFPID-1439319", "CSAFPID-1453381", "CSAFPID-1453382", "CSAFPID-2858634", "CSAFPID-2858635", "CSAFPID-5984702", "CSAFPID-5984703", "CSAFPID-5984704", "CSAFPID-5984705" ] } ], "title": "CVE-2026-23417" } ] }