From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80607][LOW] tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg [ Upstream Date: Fri, 28 Aug 2026 07:09:38 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80607 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: f148f86c65b8f9ef2466ad8506e721749e4957fb List-Id: CVE: CVE-2026-80607 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg [ Upstream Commit: f148f86c65b8f9ef2466ad8506e721749e4957fb Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f148f86c65b8f9ef2466ad8506e721749e4957fb Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80607 Analysis date: Fri, 28 Aug 2026 07:09:38 -0400 ActionableScore: 2 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: A local user with tracing permissions can trigger a reachable WARN_ON_ONCE in parse_btf_arg when creating a kprobe event with a raw address and BTF parameter, causing log noise or a kernel panic only on systems configured with panic_on_warn. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80607 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80607 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: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-80607 LOW CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-617;CWE-703;CWE-755;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'parse_btf_arg contains a user reachable WARN_ON_ONCE in the tracing probe argument parser. A local user who can create kprobe events with BTF parameters based on a raw address can trigger the warning through tracefs control plane input. For the CVSS the PR:H is typical because creating such tracing events usually requires administrator level tracing access such as CAP_SYS_ADMIN or equivalent tracefs permissions. The issue is not network reachable and there is no evidence of memory corruption, information disclosure, or privilege escalation. Impact is normally limited to a kernel warning and log noise, but systems configured with panic_on_warn may convert the warning into a local denial of service via kernel panic.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) SKIP CVE-2026-80607 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE OOB TRACE SIMPLEFIX LINUS LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like** ## 2. Signal breakdown Conservative signals: * Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2. Creating kprobe events through tracing/tracefs normally requires administrator-level tracing permissions. * WARN_ON continuation only: +0. The patch removes a reachable WARN_ON_ONCE but does not show UAF, OOB access, double free, type confusion, data leak, or later crash in normal configuration. * No network reachability: +0. This is a local tracing control-plane path. Paranoid signals: * Local delegated trigger: +1. If tracefs or tracing control is delegated to a less privileged local user or service, the warning becomes locally reachable without full host-root control. * Reliable kernel crash / strong DoS under panic_on_warn: +1. Systems configured with panic_on_warn can turn this reachable warning into a kernel panic. * Non-default panic behavior limits severity: no extra availability point. The crash depends on panic_on_warn or similar hardening/debug policy, not on the normal return path. ## 3. Reachability analysis The bug can be triggered by a local actor able to add a kprobe event based on a raw address with a BTF parameter. In typical deployments this requires root, CAP_SYS_ADMIN, or equivalent tracefs permissions, so the conservative interpretation is low practical risk. Containers and delegated tracing setups can reduce the effective privilege requirement, but tracefs is usually not exposed to untrusted users. The affected path is not network reachable and is not a common packet or filesystem data path. ## 4. Severity interpretation This behaves like an ordinary Moderate or Low-like issue, not an Important-class vulnerability. The demonstrated primitive is a user-reachable WARN_ON_ONCE followed by returning EINVAL, not memory corruption or a privilege-escalation primitive. The realistic impact is warning/log noise, with DoS only on systems where panic_on_warn is enabled. ## 5. One-sentence report phrase A local user with tracing permissions can trigger a reachable WARN_ON_ONCE in parse_btf_arg when creating a kprobe event with a raw address and BTF parameter, causing log noise or a kernel panic only on systems configured with panic_on_warn. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This can be autoclosable for most triage workflows because it is a reachable warning only, requires privileged tracing access in typical deployments, is not network reachable, and has no supported memory corruption or privilege escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: tracing/probes: Remove WARN_ON_ONCE from parse_btf_arg [ Upstream Commit: f148f86c65b8f9ef2466ad8506e721749e4957fb Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f148f86c65b8f9ef2466ad8506e721749e4957fb Changed files: kernel/trace/trace_probe.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=f148f86c65b8f9ef2466ad8506e721749e4957fb ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80607 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80607 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:L/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 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: 0 Paranoid ActionableScore: 2 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: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW 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).