From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98965][MODERATE REGULAR] ice: Restore Ordered MMIO Writes for Tx Doorbells [ Upstream Date: Mon, 26 Oct 2026 22:42:45 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98965 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: b7725acf9c574debb97ae1613569ac9e148438be List-Id: CVE: CVE-2026-98965 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: ice: Restore Ordered MMIO Writes for Tx Doorbells [ Upstream Commit: b7725acf9c574debb97ae1613569ac9e148438be Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7725acf9c574debb97ae1613569ac9e148438be Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98965 Analysis date: Mon, 26 Oct 2026 22:42:45 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: An arm64 ICE transmit-doorbell ordering race can reliably expose stale DQL accounting and trigger a host kernel BUG under sustained network transmission. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98965 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98965 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 REGULAR 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-98965 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98965 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=MODERATE RESULT=DIFF (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-362;CWE-662;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.3';DESCR 'An MMIO ordering race in the ice transmit path can allow the NIC to process and complete descriptors before the earlier DQL num_queued accounting update becomes globally visible on arm64. dql_completed can then observe more completed bytes than queued bytes and trigger a BUG_ON, causing a host kernel crash under sustained transmit load. The confirmed conditions include an affected Intel ICE adapter, arm64 memory ordering, the vulnerable driver version, and sufficient traffic to expose the timing window. For the CVSS the PR:N value in the paranoid vector assumes an adjacent attacker can induce sustained transmit traffic through an exposed service without local code execution. No UAF, OOB access, information disclosure, or arbitrary write primitive is supported by the code change, so confidentiality and integrity remain unaffected. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 5.3 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. 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. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 5.3 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE REMOTE DANGER RACE NETWORK KERNEL_PANIC_PLUS_UAF HARDWARE TEST DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED 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; speculative adjacent-network triggering is not scored. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash / strong DoS: the missing normal-memory-to-MMIO ordering lets the NIC complete descriptors before `dql->num_queued` is visible, causing a confirmed `BUG_ON()` and host Oops under sustained load. * 0 Race penalty: although timing-dependent, the failure reproduced reliably under sustained traffic; no narrow or one-shot race is shown. * 0 Remote-reachability bonus: the hints’ adjacent attacker scenario is an assumption. No exposed service or traffic pattern proving attacker control of the required transmit workload is supplied. * 0 additional availability: the same kernel crash is not counted twice. * No UAF, OOB write, shared-backing write, authorization bypass, disclosure, or integrity primitive is shown. NEW52/B5-R, NEW53/B3-PENDING, and NEW54/B4-PENDING do not apply. 3. Reachability analysis The confirmed environment requires an affected Intel ICE adapter, arm64 ordering behavior, the vulnerable driver, and sustained transmission. Who can generate the necessary workload is unresolved: ordinary remote traffic might induce replies in some deployments, while local workload or configured services may be needed in others. No capability check, namespace-complete trigger, host-admin requirement, prior privileged setup beyond normal NIC configuration, or attacker-controlled race sequence is established. 4. Primitive and severity reading The primitive is an MMIO ordering failure producing transiently inconsistent DQL accounting, followed by an intentional `BUG_ON()`. This is CLASS_C crash/DoS behavior, not memory corruption or corrupted active state consumed for a non-crash operation. The patch restores ordering with `writel()`. Important-grade leverage and protected-state impact are unsupported, so automatic Important preservation is unnecessary. 5. One-sentence report phrase An arm64 ICE transmit-doorbell ordering race can reliably expose stale DQL accounting and trigger a host kernel BUG under sustained network transmission. 6. Manual review advice MANUAL CHECK RECOMMENDED Confirm affected adapter/architecture exposure and whether an untrusted network peer can reliably induce the required outbound transmit load in the assessed deployment. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ice: Restore Ordered MMIO Writes for Tx Doorbells [ Upstream Commit: b7725acf9c574debb97ae1613569ac9e148438be Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b7725acf9c574debb97ae1613569ac9e148438be Changed files: lib/dynamic_queue_limits.c drivers/net/ethernet/intel/ice/ice_txrx.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=b7725acf9c574debb97ae1613569ac9e148438be ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98965 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98965 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:H The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.3 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: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).