From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98791][MODERATE REGULAR] net/mlx5e: Fix AF_XDP TX timestamp teardown NULL dereference [ Upstream Date: Mon, 19 Oct 2026 01:07:42 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98791 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: fce70b6bf9f3261e887419a4e7caa25b80fa9d55 List-Id: CVE: CVE-2026-98791 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: net/mlx5e: Fix AF_XDP TX timestamp teardown NULL dereference [ Upstream Commit: fce70b6bf9f3261e887419a4e7caa25b80fa9d55 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fce70b6bf9f3261e887419a4e7caa25b80fa9d55 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98791 Analysis date: Mon, 19 Oct 2026 01:07:42 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: An outstanding AF_XDP TX descriptor requesting a timestamp can pass a NULL CQE to the mlx5e timestamp helper during queue teardown, causing a local kernel Oops or possible panic without evidence of memory corruption or privilege escalation. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98791 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98791 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-98791 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98791 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=MODERATE RESULT=DIFF V39_AEGIS_ONE_STEP_UP=LOW->MODERATE TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC) 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-754;*CWE-20;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference in the mlx5e AF_XDP TX timestamp path can occur during XSK TX queue teardown. Outstanding descriptors are completed without a CQE, but a descriptor that requested a TX timestamp can still reach mlx5e_xsk_fill_timestamp and pass the NULL CQE to get_cqe_ts. For the CVSS the PR:L value is selected because triggering requires a local process with access to an AF_XDP queue, although creating or configuring that queue may also require capabilities or prior administrative setup. The issue is not directly network reachable because ordinary packet traffic does not by itself control AF_XDP queue teardown or timestamp requests. Impact is a local denial of service through a driver failure or kernel Oops, with a possible system wide kernel panic when panic_on_oops is enabled. The available code shows a NULL dereference and does not provide evidence of UAF, OOB access, information disclosure, controlled memory corruption, or privilege escalation. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 5.5 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. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to MODERATE because the cross model evidence reconciliation 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 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 3.3 and ActionableScore 0 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE REMOTE NULLPTR SIMPLEFIX NETWORK DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 PrimitiveClass=CLASS_C 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 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 fault or DoS. Queue teardown can deterministically pass a NULL CQE to `get_cqe_ts()`, causing a kernel Oops and potentially a panic when `panic_on_oops` is enabled. * +0 Additional availability. Not awarded because driver disruption, Oops, and possible panic are consequences of the same NULL dereference. * +0 Local unprivileged trigger. AF_XDP queue access is required, but the supplied evidence does not establish that an ordinary user can complete XDP loading, attachment, queue setup, timestamp request, and teardown. * +0 Memory corruption. The primitive is a NULL read dereference, not UAF, OOB access, arbitrary write, repeated release, or corrupted active state. * +0 Confidentiality and integrity. No disclosure, unauthorized modification, shared-backing write, or security-boundary bypass is established. * +0 Hardware penalty. mlx5 hardware is required, but the evidence does not establish that it is rare or physical-attacker controlled. * +0 Timing penalty. This is an ordered teardown condition, not an established hard race. * V32, V33, and V34 do not apply. No attacker-influenced checksum placement, header overwrite, active structured-state corruption, or privileged downstream metadata consumer exists. * NEW52 B5-R does not apply. There is no heap OOB write, retry-accumulated index, or later consumption of corrupted structured state. * NEW53 B3-PENDING does not apply. There is no write to shared or file-backed storage. * NEW54 B4-PENDING does not apply. No authorization guard or DENY-to-ALLOW decision is changed. ## 3. Reachability analysis The trigger requires an mlx5e AF_XDP TX queue, an outstanding descriptor requesting a TX timestamp, and queue teardown before a CQE is available. Ordinary network packets cannot directly select the timestamp callback state or initiate the required AF_XDP teardown. The complete privilege chain is unresolved. AF_XDP data-plane access may be delegated, while XDP program loading, attachment, netdevice control, and queue provisioning may require separate capabilities or prior administrative setup. The supplied patch does not establish whether all stages are available below host-admin privilege or within an attacker-created user and network namespace. Therefore `HostAdminRequired` and `NamespaceScopedPrivilege` remain `UNKNOWN`. No race is required. Once the relevant descriptor remains outstanding during teardown, the missing CQE is passed directly to the timestamp helper. ## 4. Primitive and severity interpretation The exact primitive is a cleanup-path NULL pointer dereference. During teardown, completion is performed without a CQE, but `mlx5e_xsk_fill_timestamp()` previously called `get_cqe_ts(priv->cqe)` unconditionally. This is neither active structured-state corruption nor stale storage. No object has been freed and reused, no lifetime reference is released twice, and no attacker-controlled state is written through the NULL pointer. The demonstrated consequence is an Oops, driver or interface disruption, and a possible host panic under fatal-Oops policy. Privilege escalation, information disclosure, controlled memory corruption, and cross-boundary impact are unsupported. `ImportantCandidate=NO` because no Important-preserving primitive remains unresolved. `AutoDowngradeAllowed=YES` because the defect is a constrained Class C teardown dereference with crash-only impact. ## 5. One-sentence report phrase An outstanding AF_XDP TX descriptor requesting a timestamp can pass a NULL CQE to the mlx5e timestamp helper during queue teardown, causing a local kernel Oops or possible panic without evidence of memory corruption or privilege escalation. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED The direct primitive is a constrained NULL dereference, and none of the UAF, OOB-write, authorization, shared-backing, active-state, or cross-boundary preservation rules apply. ## 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: net/mlx5e: Fix AF_XDP TX timestamp teardown NULL dereference [ Upstream Commit: fce70b6bf9f3261e887419a4e7caa25b80fa9d55 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fce70b6bf9f3261e887419a4e7caa25b80fa9d55 Changed files: drivers/net/ethernet/mellanox/mlx5/core/en/xdp.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=fce70b6bf9f3261e887419a4e7caa25b80fa9d55 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98791 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98791 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:L/UI:N/S:U/C:N/I:N/A:L 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: 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).