From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98034][MODERATE 7.0] bpf: Mark NULL kptr stores precise [ Upstream Date: Fri, 25 Sep 2026 15:01:57 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98034 X-AL-KERNEL-Priority: MODERATE 7.0 X-AL-KERNEL-Severity: MODERATE 7.0 X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: YES X-AL-KERNEL-ActionableScore: 5 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 86168208737bdd267d92d855d453d1d2f840df19 List-Id: CVE: CVE-2026-98034 Priority: MODERATE 7.0 AL-KERNEL base severity: MODERATE KPANIC flag: YES Patch: bpf: Mark NULL kptr stores precise [ Upstream Commit: 86168208737bdd267d92d855d453d1d2f840df19 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=86168208737bdd267d92d855d453d1d2f840df19 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98034 Analysis date: Fri, 25 Sep 2026 15:01:57 -0400 ActionableScore: 5 ActionableScore lower bound: unknown Actionable bucket: Actionable Moderate / Strong Important candidate requiring manual review Manual review required: YES Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98034 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98034 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE 7.0 Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-98034 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98034 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-1284;CWE-843;CWE-822;CWE-284;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';BEST CVSS score: '7.8';DESCR 'A BPF verifier state pruning flaw can allow a scalar register accepted as a known zero for an untrusted kptr store to reach the same store with attacker controlled nonzero bits. The stored value can then be loaded as PTR_TO_BTF_ID, creating a type confusion condition and a plausible kernel memory corruption primitive. For the CVSS the PR:L rating reflects that an attacker must execute a local process able to load the affected BPF program. This may be an unprivileged account where unprivileged BPF is enabled or a constrained account with delegated BPF capability. The issue is not directly network reachable. Impact may include local privilege escalation, arbitrary kernel memory access, or kernel crash. YES REQUIRES MANUAL CHECK.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate / Strong Important candidate requiring manual review (with actual score 5) YES INIT BPF SIMPLEFIX IMPROVEONLY LINUS KPANIC INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK YES NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=5 PrimitiveClass=CLASS_A RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=YES ManualReview=REQUIRED AutoDowngradeAllowed=NO 1. ActionableScore * Raw conservative score: 2 * Conservative score: 5 * Raw paranoid score: 3 * Paranoid score: 5 * Applied conservative floor: 2 -> 5 because a concrete attacker-controlled scalar to PTR_TO_BTF_ID semantic reinterpretation is established and must not be automatically closed below Actionable Moderate. * Applied paranoid floor: 3 -> 5 for the same reason. * Final recommended bucket: **Actionable Moderate / Strong Important candidate requiring manual review**:: 2. Signal breakdown * +2 Strong attacker-influenced semantic reinterpretation. The verifier can accept a path where a register is known zero, prune a path where that register is nonzero, and permit attacker-controlled scalar bits to be stored in an untrusted kptr field and subsequently loaded as PTR_TO_BTF_ID. * +1 Paranoid only. The reinterpreted value is an active typed kernel pointer representation. This creates a technically defensible possibility of later BPF memory access through a forged pointer, but the supplied patch does not show the specific later dereference or an arbitrary read or write sink. Important non-awarded signals: * Local unprivileged trigger not awarded. The supplied evidence does not establish that the complete kptr map creation, BPF program loading, and trigger sequence is usable by an ordinary unprivileged user in the evaluated product. * BPF high-control API bonus not awarded. BPF is attacker-controlled after loading, but below-host-admin reachability of the complete relevant BPF setup is not established. * Remote reachability not established. This is a local BPF verifier path, not a packet-processing trigger. * Controlled reclaim, UAF, double free, refcount takeover, callback control, arbitrary kernel write, and demonstrated arbitrary kernel read are not established. * Demonstrated local privilege escalation is not established by the patch alone. * Reliable kernel crash is not directly demonstrated, so no separate DoS point is awarded. * Confidentiality and integrity impact are not separately awarded. The forged pointer primitive is serious, but the supplied evidence does not demonstrate a successful disclosure or modification operation. * No privilege penalty is applied. Host-admin-equivalent privilege is not positively established, but below-host-admin reachability is also not proven. 3. Reachability analysis The evaluated attacker is a local process that can load a BPF program using maps with untrusted kptr fields. The vulnerable verifier path is reached during program verification, before the program is accepted and executed. The complete privilege boundary is unresolved from the supplied patch. Modern distributions frequently restrict unprivileged BPF, and kptr-enabled BPF map and program operations may require CAP_BPF, CAP_SYS_ADMIN, additional verifier permissions, or product-specific policy approval. The patch does not establish whether those checks are host-user-namespace scoped, delegable into a container, or reachable by an ordinary user. No XDP attachment, network device control, physical device, firmware, boot parameter, or remote traffic is required by the shown verifier bug itself. However, the absence of those requirements does not prove that an ordinary local user can complete the required BPF load and map setup sequence. 4. Primitive and severity interpretation The exact primitive is a verifier state-equivalence failure. A scalar value accepted as zero for an untrusted kptr store is not marked precise. State pruning can then incorrectly treat a path carrying an attacker-controlled nonzero scalar as equivalent to the zero-valued path. The attacker-controlled scalar bits can be stored in a kptr field and later loaded under PTR_TO_BTF_ID semantics. This is not a UAF, cleanup bug, stale reference, or crash-only invalid pointer dereference. It is a controlled type confusion and semantic pointer reinterpretation primitive. The relevant security boundary is the BPF verifier rule that restricts untrusted kptr stores to NULL values. The patch directly establishes the scalar-to-pointer semantic conversion. It does not directly establish controlled reclaim, arbitrary read, arbitrary write, function pointer control, credential modification, or a completed privilege-escalation chain. Therefore, the practical consequence remains unresolved rather than proven. PrimitiveClass is CLASS_A because the patch establishes attacker-controlled semantic reinterpretation into an active kernel pointer type. ImportantCandidate is YES because verifier-bypass pointer forgery requires security review even though the complete exploitation chain is not supplied. AutoDowngradeAllowed is NO because automatically treating this as an ordinary verifier validation defect would discard a concrete pointer-type confusion primitive. Likely operational severity is Actionable Moderate at minimum. It is a strong Important candidate if follow-up analysis confirms that the forged PTR_TO_BTF_ID can be dereferenced, passed to a relevant kfunc, used to access an attacker-selected BTF object, or reached by ordinary unprivileged users under the target product policy. 5. One-sentence report phrase A BPF verifier state-pruning flaw can reinterpret attacker-controlled scalar bits stored in an untrusted kptr field as PTR_TO_BTF_ID, creating a controlled kernel pointer type-confusion primitive that requires manual exploitation review. 6. Manual review recommendation MANUAL CHECK REQUIRED The patch establishes a concrete verifier bypass that converts attacker-controlled scalar data into a kernel pointer representation, while the downstream pointer-use capabilities and actual BPF privilege boundary remain unresolved. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: bpf: Mark NULL kptr stores precise [ Upstream Commit: 86168208737bdd267d92d855d453d1d2f840df19 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=86168208737bdd267d92d855d453d1d2f840df19 Changed files: kernel/bpf/verifier.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=86168208737bdd267d92d855d453d1d2f840df19 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98034 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98034 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS score: 7.8 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 5 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: YES Published priority for this report (same as in Subject): MODERATE 7.0 These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).