From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-80689][LOW] tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions [ Upstream Date: Fri, 28 Aug 2026 07:36:05 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-80689 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: 1 X-AL-KERNEL-ActionableScore-Lower: 0 X-AL-KERNEL-Commit: 876014b4eeb927146430e7591cf959a7ceb8d64a List-Id: CVE: CVE-2026-80689 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions [ Upstream Commit: 876014b4eeb927146430e7591cf959a7ceb8d64a Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=876014b4eeb927146430e7591cf959a7ceb8d64a Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80689 Analysis date: Fri, 28 Aug 2026 07:36:05 -0400 ActionableScore: 1 ActionableScore lower bound: 0 Actionable bucket: Ordinary Moderate / Low-like Manual review required: YES Summary: A NULL pointer dereference in mmiotrace logging can crash the kernel if MMIO trace events are logged while mmio_trace_array is NULL, but triggering normally requires local administrative tracing control and the issue is not network reachable. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80689 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80689 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: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-80689 LOW CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'mmiotrace logging can dereference a NULL trace_array because mmio_trace_array may be NULL when mmio_trace_rw() or mmio_trace_mapping() forwards events to the internal trace helpers. This can happen before initialization or after mmiotrace has been disabled, and the helpers would access tr array_buffer buffer before validating tr. For the CVSS the PR:L is used in the paranoid score because a reduced-capability admin, service account, or delegated tracing operator may be able to toggle tracing without full host admin control. The issue is not network reachable and requires local control of tracing or mmiotrace state. Impact is denial of service via kernel crash only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) YES NULLPTR TRACE SIMPLEFIX HARDWARE LINUS NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 ActionableScoreLower=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 1 * Final recommended bucket: **Ordinary Moderate / Low-like** ## 2. Signal breakdown * Reliable kernel crash / strong DoS: +1 The patch prevents a direct NULL pointer dereference of `tr->array_buffer.buffer` when `mmio_trace_array` is NULL. * Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2 mmiotrace and tracing control paths are normally restricted to root or tracing-capable administrative users. * Rare AND difficult-to-reach subsystem/configuration: -1 mmiotrace is a specialized tracing/debug facility and is not a common default attack surface. * Paranoid privilege refinement: +1 relative to conservative handling In some environments tracing control may be delegated to a reduced-capability operator or service account, so the practical PR can be lower than full host root. This does not make it unprivileged. No UAF, OOB access, refcount misuse, stale callback, type confusion, arbitrary write, or ownership/COW bypass is shown by the patch. ## 3. Reachability analysis The bug is local and requires the mmiotrace logging path to run while `mmio_trace_array` is NULL, for example before initialization or after mmiotrace has been disabled. In normal deployments, enabling or disabling mmiotrace is an administrative tracing operation. Containers and namespaces do not usually expose this path to unprivileged users unless the host deliberately delegates tracing/debugfs access. The path is not network reachable and is not part of a common packet, filesystem, or syscall data-plane interface. Call-site confidence: medium. The changed functions and immediate dereference are visible, but wider triggering paths are inferred from mmiotrace/tracing behavior. ## 4. Severity interpretation This behaves like an ordinary Moderate or Low-like kernel hardening fix rather than an Important vulnerability. The demonstrated primitive is a NULL pointer dereference leading to DoS. There is no evidence of exploitable memory corruption, privilege escalation, information disclosure, or integrity impact. The paranoid interpretation only lowers the practical privilege assumption to a delegated local tracing operator, but still keeps the impact as DoS-only. ## 5. One-sentence report phrase A NULL pointer dereference in mmiotrace logging can crash the kernel if MMIO trace events are logged while mmio_trace_array is NULL, but triggering normally requires local administrative tracing control and the issue is not network reachable. ## 6. Manual review recommendation NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED This is a local privileged NULL dereference in a specialized tracing path with no supported memory corruption or privilege escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions [ Upstream Commit: 876014b4eeb927146430e7591cf959a7ceb8d64a Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=876014b4eeb927146430e7591cf959a7ceb8d64a Changed files: kernel/trace/trace_mmiotrace.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=876014b4eeb927146430e7591cf959a7ceb8d64a ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-80689 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80689 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:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 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: 1 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).