From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-97434][MODERATE REGULAR] dpaa2-switch: fix handling of NAPI on the remove path [ Upstream Date: Thu, 24 Sep 2026 18:28:07 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-97434 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: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 569df157eb874cb3b50554d73b89f31599397b42 List-Id: CVE: CVE-2026-97434 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: dpaa2-switch: fix handling of NAPI on the remove path [ Upstream Commit: 569df157eb874cb3b50554d73b89f31599397b42 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=569df157eb874cb3b50554d73b89f31599397b42 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97434 Analysis date: Thu, 24 Sep 2026 18:28:07 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-97434 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97434 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-97434 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-97434 CHECK WITH IMPACT FROM ORIG NN IMPORTANT Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-362;*CWE-664;*CWE-672;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'A DPAA2 switch driver teardown issue can delete NAPI instances while other switch ports are still active because the NAPI instances are shared but attached to the first port net_device. If device removal overlaps with active packet processing, the incorrect teardown order can cause NAPI lifecycle violations, network device instability, warnings, or a denial of service during removal. For the CVSS the PR:H because reliably triggering the remove path normally requires administrative permission to unbind remove or reconfigure the device. The issue is not directly network reachable because network traffic alone cannot initiate driver removal. The patch context does not demonstrate a use after free or another memory corruption primitive, so confidentiality and integrity impact are not claimed.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) YES REMOTE INIT UAF NETWORK HARDWARE LINUS LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: -1 * Conservative score: 0 * Raw paranoid score: -1 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate**:: The score is clamped to zero because the patch does not establish a memory-corruption, lifetime, authorization, disclosure, or integrity primitive. 2. Signal breakdown * -1 Rare and difficult-to-reach subsystem/configuration. The affected code is specific to NXP DPAA2 DPSW switch hardware and cannot ordinarily be instantiated by an attacker using a generic kernel interface. * +0 Reliable kernel crash or strong DoS not awarded. The commit describes deletion of enabled NAPI instances and an invalid teardown order, but does not document an Oops, panic, use-after-free, memory overwrite, device-wide unrecoverable failure, or host-wide denial of service. * +0 Real UAF not awarded. The patch changes ordering so that shared NAPI instances are disabled before deletion. It does not establish that a freed NAPI object is later dereferenced. * +0 Concrete repeated release/refcount operation not awarded. No same-reference second put, free, release, or refcount mutation is visible. * +0 Structured stale-object leverage not awarded. There is no demonstrated stale-object reuse, attacker-controlled replacement, callback consumption, or post-free field processing. * +0 Remote reachability not awarded. Incoming traffic can keep NAPI active, but it cannot itself invoke the driver remove path. * +0 Local unprivileged trigger not awarded. The supplied patch does not establish that an ordinary user can initiate device removal, driver unbind, or equivalent DPAA2 switch teardown. * +0 Host-admin penalty not applied. A host administrator can initiate driver unbind or device removal, but the evidence does not establish that this is the only way the relevant remove path can execute. The hardware can also be removed or reset through platform-managed events. * +0 Hard-race penalty not applied. This is primarily an incorrect ordered teardown sequence, not a demonstrated narrow timing race. 3. Reachability analysis The affected path is `dpaa2_switch_remove()`, which executes when the DPSW device is removed or the driver is unbound. The patch shows that the prior sequence could unregister and free the first port netdev before all shared NAPI instances had been disabled. The complete attacker-triggerable sequence is not established. A host administrator can normally trigger driver unbind or device removal through privileged device-management operations, but the supplied material does not prove that an attacker must possess host-admin-equivalent privilege because device removal may also be caused by platform, firmware, reset, or hotplug events. No namespace-scoped capability path is shown. The DPSW device is a hardware-backed switch object, and the patch does not establish that a user-created network namespace can create, remove, or fully control the required device lifecycle. `NamespaceScopedPrivilege=UNKNOWN` is therefore appropriate. The vulnerability requires DPAA2 DPSW hardware and the corresponding driver configuration. This is specialized embedded/networking hardware rather than a broadly reachable generic networking path. Packet traffic may be relevant to active NAPI processing, but traffic alone is not a complete trigger because it cannot cause the `.remove()` path. 4. Primitive and severity interpretation The patch establishes an invalid NAPI lifecycle ordering during DPAA2 switch teardown: `unregister_netdev(first port)` `-> free_netdev(first port)` `-> shared NAPI deletion while other ports remain active` The corrected ordering first unregisters all ports, which causes shared NAPI instances to become disabled when the last port goes down. Only then does the driver explicitly call `netif_napi_del()`, followed by per-port cleanup. This is an invalid-state and teardown-order bug. The patch does not establish an actual use-after-free, stale post-lifetime dereference, double deletion, double release, refcount mutation, OOB access, arbitrary write, information disclosure, or authorization bypass. The affected NAPI objects are active kernel structures, but object complexity alone is not sufficient to classify this as a lifetime-corruption primitive. The visible change prevents deletion while NAPI is still enabled. It does not show deletion followed by active NAPI polling through freed or reclaimed storage. The demonstrated practical consequence is limited to possible NAPI lifecycle violations, warnings, network-device instability, or a denial of service during device removal. A host-wide crash is not demonstrated. Privilege escalation, confidentiality impact, integrity impact, controlled object replacement, and attacker-controlled post-free contents are speculative and are not scored. `PrimitiveClass=NONE` is appropriate because no meaningful corruption, lifetime, ownership, authorization, or similar security primitive is established. `ImportantCandidate=NO` and `AutoDowngradeAllowed=YES` are appropriate because this is a constrained hardware-driver teardown issue without unresolved concrete exploitation leverage. 5. One-sentence report phrase A DPAA2 switch driver teardown ordering flaw can delete shared NAPI instances before all switch ports are down, causing invalid NAPI lifecycle handling and possible network-device instability during device removal. 6. Manual review recommendation MANUAL CHECK RECOMMENDED Review the surrounding `dpaa2_switch_remove_port()`, netdev destructor, and NAPI teardown behavior to confirm whether an enabled NAPI instance can remain scheduled or accessed after `netif_napi_del()`. The submitted patch alone does not establish a UAF or kernel memory-corruption primitive. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: dpaa2-switch: fix handling of NAPI on the remove path [ Upstream Commit: 569df157eb874cb3b50554d73b89f31599397b42 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=569df157eb874cb3b50554d73b89f31599397b42 Changed files: drivers/net/ethernet/freescale/dpaa2/dpaa2-switch.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=569df157eb874cb3b50554d73b89f31599397b42 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-97434 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97434 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:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.1 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: 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).