* [CVE-2026-99193][LOW] net: ti: icssm-prueth: Move setting of netops to fix crash [ Upstream
@ 2026-10-30 16:28 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-30 16:28 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-99193
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: net: ti: icssm-prueth: Move setting of netops to fix crash [ Upstream
Commit: e7694aab7ad002480ed9d534bd8d6bc28b798d8a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7694aab7ad002480ed9d534bd8d6bc28b798d8a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99193
Analysis date: Fri, 30 Oct 2026 12:28:52 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
A TI ICSSM PRU Ethernet probe-ordering error can dereference a NULL `netdev_ops` pointer and crash the kernel when network shaper support is enabled.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-99193 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99193
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-99193 LOW https://www.kernelcve.org/list/?q=CVE-2026-99193 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE_KPANIC) 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-476;CWE-665;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'A probe ordering bug in the TI ICSSM PRU Ethernet driver leaves ndev netdev_ops unset when of_phy_get_and_connect starts PHY attachment. With CONFIG_NET_SHAPER enabled, phy_attach_direct can reach phy_link_topo_add_phy and netdev_need_ops_lock, which reads the NULL operations pointer and can crash the kernel during device probe. For the CVSS the PR:H base value reflects that reliable triggering normally requires administrative control over driver binding, device probing, boot configuration, or the relevant hardware description. For the CVSS the PR:L paranoid value covers environments that delegate device management to a constrained administrator or a less trusted system service. The demonstrated primitive is a NULL pointer dereference with availability impact only. There is no evidence of UAF, OOB access, information disclosure, or a write primitive, and ordinary network traffic cannot reach this initialization path. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 0 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 LOW because KP specialist did not establish a qualifying panic and 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 KPANIC_UNSUPPORTED_REMOVED and V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 1.9 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 LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) MAYBE REMOTE LOCK NULLPTR SIMPLEFIX LEAK NETWORK DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=0
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO
1. ActionableScore
* Raw base score: -1.
* Conservative score: 0 after applying the score lower bound.
* Raw paranoid score: -1.
* Paranoid score: 0 after applying the score lower bound.
* Final recommended bucket: **Ordinary Moderate**::
2. Signal breakdown
* +1 — Reliable kernel crash: during device probe, PHY attachment reaches `netdev_need_ops_lock()` before `ndev->netdev_ops` is initialized, producing a supported NULL-pointer dereference with `CONFIG_NET_SHAPER`.
* -2 — Hardware-specific exposure: the path requires the TI ICSSM PRU Ethernet device, its PHY probe path, and the relevant kernel configuration.
* No UAF, OOB access, write primitive, stale lifetime state, shared backing, retry-accumulated corruption, or authorization bypass is shown.
* No remote/network-traffic bonus: ordinary packets do not reach this device-initialization ordering defect.
* No additional availability point: it would duplicate the same probe-time crash.
* No AC/race penalty: the patch shows deterministic initialization ordering, not a difficult race.
* B5-R does not apply: there is no heap OOB write, retry accumulation, or later consumption of corrupted structured state.
* B3-PENDING and B4-PENDING do not apply.
3. Reachability analysis
The defect is reached while probing and attaching the PHY, not through the runtime packet data path. Relevant hardware, device-tree/platform configuration, driver probing, and `CONFIG_NET_SHAPER` are prerequisites. Administrative control is a plausible trigger route, but the supplied evidence does not positively prove that every complete trigger requires effective host-administrator powers; therefore `HostAdminRequired=UNKNOWN`. No namespace-scoped operation or ordinary local-user interface is shown. There is no timing race.
4. Primitive and severity reading
The exact primitive is an initialization-order NULL dereference: `netdev_ops` remains NULL while PHY topology setup reads it. This is invalid-state consumption resulting in a probe-time kernel crash, classified as CLASS_C. It is neither active-state corruption nor a post-lifetime use. No useful effect remains after excluding the crash, and no confidentiality, integrity, authorization, or trust-boundary impact is evidenced. Consequently, this is not an Important candidate and can be auto-downgraded.
5. One-sentence report phrase
A TI ICSSM PRU Ethernet probe-ordering error can dereference a NULL `netdev_ops` pointer and crash the kernel when network shaper support is enabled.
6. Manual review advice
NO MANUAL CHECK NEEDED
The patch establishes a hardware-specific NULL-dereference availability bug without a corruption or security-boundary primitive.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: net: ti: icssm-prueth: Move setting of netops to fix crash [ Upstream
Commit: e7694aab7ad002480ed9d534bd8d6bc28b798d8a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7694aab7ad002480ed9d534bd8d6bc28b798d8a
Changed files:
drivers/net/ethernet/ti/icssm/icssm_prueth.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=e7694aab7ad002480ed9d534bd8d6bc28b798d8a
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-99193 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99193
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:H
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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-10-30 16:28 21% [CVE-2026-99193][LOW] net: ti: icssm-prueth: Move setting of netops to fix crash [ Upstream AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox