From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-46249][LOW] octeontx2-af: Fix PF driver crash with kexec kernel booting [ Upstream Date: Wed, 03 Jun 2026 15:00:58 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-46249 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: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: b7605b9301abc18fbbf2b0e23fdd281fc768955d List-Id: CVE: CVE-2026-46249 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: octeontx2-af: Fix PF driver crash with kexec kernel booting [ Upstream Commit: b7605b9301abc18fbbf2b0e23fdd281fc768955d Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7605b9301abc18fbbf2b0e23fdd281fc768955d Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46249 Analysis date: Wed, 03 Jun 2026 15:00:58 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46249 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46249 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-46249 LOW CHECK 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-459;CWE-665;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A stale RVUM block revision can remain after kexec because hardware is not power cycled and AF state from the previous kernel may persist. If AF and PF drivers are loaded as modules, the PF driver can probe before AF reinitializes the hardware and can treat the stale revision value as proof that AF is ready. This can make the PF driver access stale hardware state and crash the kernel during boot. For the CVSS the PR:L is used only in the paranoid view for environments where reboot or kexec control is delegated to a limited operator or service account. The issue is not network reachable and the impact is denial of service only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0) MAYBE REMOTE DANGER INIT SIMPLEFIX NETWORK KERNEL_PANIC_PLUS_UAF HARDWARE BOOT DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 1. ActionableScore * Conservative score: 0 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate / Low-like** 2. Signal breakdown * Reliable kernel crash / strong DoS: +1. PF may access stale AF hardware state after kexec and crash during boot. * Requires admin/root/CAP_SYS_BOOT/CAP_SYS_MODULE in typical deployments: -2. Triggering requires kexec reboot and driver/module ordering control in normal systems. * Physical-only or rare hardware-only condition: -2. The issue is specific to Marvell OcteonTX2 RVU AF/PF hardware and kexec without power cycling. * Rare AND difficult-to-reach subsystem/configuration: -1. It requires AF and PF drivers as modules plus PF probing before AF reinitialization. * Score is floored at 0. No memory corruption, privilege escalation, network reachability, or security-boundary bypass is supported by the patch. 3. Reachability analysis The bug is triggerable only in a local administrative reboot path involving kexec. A normal unprivileged user cannot initiate kexec or control kernel driver probe ordering. Namespace or container delegation does not normally make this reachable unless a management system explicitly grants reboot or kexec control, which would still make this a reliability risk rather than a direct isolation bypass. The affected path is not default network reachable and depends on specific Marvell hardware plus module load timing after kexec. 4. Severity interpretation This behaves like a Low-like reliability DoS rather than an actionable Moderate or Important kernel vulnerability. The patch prevents stale hardware readiness state from surviving into the next kexec kernel. The realistic impact is a boot-time PF driver crash. There is no demonstrated UAF, OOB write, attacker-controlled corruption primitive, sensitive data exposure, or privilege escalation path. 5. One-sentence report phrase A stale RVUM block revision after kexec can make the OcteonTX2 PF driver misdetect AF readiness and crash during boot, but exploitation normally requires local administrative kexec control and specific hardware/module ordering. 6. Manual review recommendation NO MANUAL CHECK NEEDED. This is hardware-specific, admin-triggered, not network reachable, and DoS-only with no supported memory corruption or privilege escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: octeontx2-af: Fix PF driver crash with kexec kernel booting [ Upstream Commit: b7605b9301abc18fbbf2b0e23fdd281fc768955d Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7605b9301abc18fbbf2b0e23fdd281fc768955d Changed files: drivers/net/ethernet/marvell/octeontx2/af/rvu.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=b7605b9301abc18fbbf2b0e23fdd281fc768955d ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46249 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46249 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: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: 0 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).