From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-90080][LOW] octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup [ Upstream Date: Thu, 17 Sep 2026 20:31:39 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-90080 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: b003d5b4e46ca5033859db601e12d36da24d0e40 List-Id: CVE: CVE-2026-90080 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup [ Upstream Commit: b003d5b4e46ca5033859db601e12d36da24d0e40 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b003d5b4e46ca5033859db601e12d36da24d0e40 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90080 Analysis date: Thu, 17 Sep 2026 20:31:39 -0400 ActionableScore: 1 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-90080 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90080 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-90080 LOW https://www.kernelcve.org/list/?q=CVE-2026-90080 CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;CWE-824;CWE-754;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'The Marvell OcteonTX2 PF driver can dereference a NULL af_xdp_zc_qidx bitmap because representors and other paths without AF_XDP do not allocate this object, while several RSS, ethtool, XSK, and pool initialization paths call test_bit on it unconditionally. A reliable trigger is switching the devlink eswitch mode so that representors are created and otx2_init_hw_resources reaches otx2_pool_aq_init, resulting in a kernel oops and denial of service. For the CVSS the PR:L reflects the paranoid interpretation where network administration is delegated to a container, service account, or otherwise restricted local operator rather than requiring unrestricted host root access. The issue is not directly network reachable because packet traffic alone is not shown to enter the failing setup path. Exploitation requires a supported Marvell OcteonTX2 device, the affected driver, and access to a relevant local control path. The demonstrated primitive is a NULL pointer invalid read with availability impact only. There is no supported UAF, OOB write, information disclosure, or privilege escalation primitive in the provided code.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) SKIP CVE-2026-90080 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES NO NO unknown MAYBE REMOTE INIT SIMPLEFIX NETWORK LINUS TEST DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES 1. ActionableScore * Raw conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap was applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash / strong DoS. Switching the devlink eswitch mode creates representors and reaches `otx2_pool_aq_init()`, where `test_bit()` dereferences the NULL bitmap and produces a kernel Oops. * +0 Weak corruption concern. This is a NULL-pointer invalid read without a useful corruption primitive. * No privilege penalty. The documented trigger is a devlink control-plane operation, but the supplied evidence does not fully resolve whether the complete operation always requires host-admin-equivalent authority or can be delegated. * No hardware penalty. An OcteonTX2 device is required, but the evidence does not establish that the applicable hardware is sufficiently rare to justify a numeric penalty. * Remote reachability not established. Network packets alone are not shown to reach the vulnerable operation. * Local unprivileged reachability not established. * Controlled reclaim, UAF, OOB access, arbitrary write, disclosure, and privilege escalation are not demonstrated. * No additional Availability point was awarded because it would duplicate the same kernel Oops. * No paranoid point was added because a stronger consequence would require an unsupported additional primitive. 3. Reachability analysis The directly documented trigger switches the devlink eswitch mode on an affected Marvell OcteonTX2 PF, creates representors, and initializes their hardware resources. This requires a supported device, the affected driver, and access to the relevant devlink control operation. The exact capability check and governing user namespace are not visible. Therefore, host-admin-equivalent privilege is not positively established, but neither is a complete below-host-admin or namespace-scoped trigger. Delegation to a network-management service or container remains possible but unproven. Prior availability and configuration of the physical PF are prerequisites. No race or timing condition is involved, and the NULL dereference is deterministic once the affected path is reached. 4. Primitive and severity interpretation The exact primitive is a NULL-pointer invalid read through `test_bit()` when `af_xdp_zc_qidx` was never allocated for a representor or another non-AF_XDP path. It is neither stale storage nor an active structured-object UAF. No object lifetime has ended, and no repeated release or refcount operation exists. The demonstrated consequence is a kernel Oops and denial of service. The patch does not establish attacker-controlled memory corruption, persistent device DMA corruption, information disclosure, or integrity impact. A stronger consequence would require a separate unsupported bug or primitive. This is CLASS_C because the behavior is an invalid-state dereference with crash impact only. ImportantCandidate is NO because no meaningful exploitation leverage beyond the fault is unresolved. AutoDowngradeAllowed is YES because the issue is a hardware-dependent local control-path DoS without a lifetime, ownership, authorization, or controlled-corruption primitive. 5. One-sentence report phrase The OcteonTX2 PF driver can dereference a NULL AF_XDP queue bitmap while creating representors, causing a local kernel Oops and denial of service without a demonstrated memory corruption or privilege escalation primitive. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch and visible call sites establish a deterministic NULL dereference with availability impact only, and no unresolved corruption or security-boundary primitive remains. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: octeontx2-pf: fix NULL deref of af_xdp_zc_qidx on rep setup [ Upstream Commit: b003d5b4e46ca5033859db601e12d36da24d0e40 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b003d5b4e46ca5033859db601e12d36da24d0e40 Changed files: drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c drivers/net/ethernet/marvell/octeontx2/nic/otx2_ethtool.c drivers/net/ethernet/marvell/octeontx2/nic/otx2_xsk.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=b003d5b4e46ca5033859db601e12d36da24d0e40 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-90080 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90080 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:L/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 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).