From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98904][LOW] mailbox: imx: Use devm_pm_runtime_enable() [ Upstream Date: Tue, 27 Oct 2026 02:16:46 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98904 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: unknown X-AL-KERNEL-Commit: b30a047744ea4344bb6f854b0a052cf276349128 List-Id: CVE: CVE-2026-98904 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: mailbox: imx: Use devm_pm_runtime_enable() [ Upstream Commit: b30a047744ea4344bb6f854b0a052cf276349128 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b30a047744ea4344bb6f854b0a052cf276349128 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98904 Analysis date: Tue, 27 Oct 2026 02:16:46 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: An i.MX mailbox probe-ordering flaw can expose a controller before runtime-PM setup completes, plausibly disrupting the device without a demonstrated kernel-corruption or host-wide crash primitive. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98904 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98904 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-98904 LOW https://www.kernelcve.org/list/?q=CVE-2026-98904 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both 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-362;CWE-665;CWE-826;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'An initialization and teardown ordering flaw registers the i.MX mailbox controller before runtime PM setup is complete, so an in kernel mailbox consumer can begin using the device before probe finishes. Error handling can also disable runtime PM before managed controller removal. The demonstrated primitive is premature device access and an inconsistent power state. No UAF, OOB access, information leak, arbitrary write, or confirmed host wide panic is established. The attack vector is local and AC:H reflects dependence on probe, consumer binding, or removal timing. For the CVSS the PR:L value is a conservative choice for a local actor able to influence mailbox consumer binding or the device lifecycle, while ordinary unprivileged code does not appear to have a direct trigger. Base impact is limited device availability. The paranoid score allows host availability loss only if the ordering fault reaches a driver crash. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. The independent weaker Aegis shadow evaluated CVSS 0.0 and ActionableScore 0 with primitive class NONE and manual review REQUIRED. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE INIT HARDWARE LINUS - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw base score: 1. * Conservative score: 1; no floor or cap applied. * Raw paranoid score: 1. * Paranoid score: 1; a host crash is not sufficiently evidenced for an additional point. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 device availability plausible: mailbox registration before runtime-PM initialization permits premature consumer access, while the old teardown order could disable runtime PM before managed controller removal. * No UAF, OOB access, overwrite, stale lifetime operation, authorization bypass, or protected-state corruption is shown. * Reliable kernel crash was not awarded: neither the patch nor supplied evidence identifies a concrete faulting operation or host-wide panic. * No race penalty: timing sensitivity is described, but materially narrow or uncontrollable timing is not established. * B5-R and B3-PENDING do not apply; there is no heap OOB write or shared-backing write. * No confidentiality, integrity, LPE, remote-reachability, or unprivileged-trigger points were awarded. 3. Reachability analysis The visible path is platform-device probe, managed mailbox registration, runtime-PM setup, and removal ordering. An in-kernel mailbox consumer may access the controller before probe completes, but the evidence does not identify a userspace interface able to induce the complete sequence. Required credentials, UID, namespace capability scope, prior device-tree/platform setup, and attacker control over binding or removal are unresolved. The issue is hardware-specific, but the evidence does not establish rare physical access, so no hardware penalty applies. 4. Primitive and severity reading The patch fixes initialization and teardown ordering, not a demonstrated memory-corruption or lifetime primitive. The shown effect is premature device use and inconsistent power-management state, with device malfunction plausible. A kernel crash remains speculative. There is no authorization DENY-to-ALLOW transition or protected resource. Therefore ImportantCandidate is NO and automatic downgrade is allowed. 5. One-sentence report phrase An i.MX mailbox probe-ordering flaw can expose a controller before runtime-PM setup completes, plausibly disrupting the device without a demonstrated kernel-corruption or host-wide crash primitive. 6. Manual review advice NO MANUAL CHECK NEEDED The patch supports only constrained initialization/power-state availability impact. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: mailbox: imx: Use devm_pm_runtime_enable() [ Upstream Commit: b30a047744ea4344bb6f854b0a052cf276349128 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b30a047744ea4344bb6f854b0a052cf276349128 Changed files: drivers/mailbox/imx-mailbox.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=b30a047744ea4344bb6f854b0a052cf276349128 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98904 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98904 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:N/I:N/A:L 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: unknown 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).