* [CVE-2025-68192][MODERATE REGULAR] net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup [ Upstream
@ 2026-10-28 14:36 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-28 14:36 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2025-68192
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup [ Upstream
Commit: d693c47fb902b988f5752182e4f7fbde5e6dcaf9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d693c47fb902b988f5752182e4f7fbde5e6dcaf9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-68192
Analysis date: Wed, 28 Oct 2026 10:36:21 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES
Summary:
Remote IPsec traffic over an affected QMAP interface can drive XFRM to consume an uninitialized skb MAC-header offset and crash strict-alignment ARM kernels.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2025-68192 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-68192
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: YES
A detailed explanation of the methodology and priority rules is included
at the end of this message.
======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================
CVE-2025-68192 MODERATE https://www.kernelcve.org/list/?q=CVE-2025-68192 CHECK WITH IMPACT FROM ORIG NN LOW | 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-665;*CWE-457;CWE-754;Other CVSS 'AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.5';DESCR 'Raw IP skbs created by qmimux_rx_fixup could retain an uninitialized MAC header offset even though the packet has no Ethernet header. XFRM or another downstream subsystem may access this offset and derive a misaligned address, causing an ARM64 alignment fault and kernel panic when IPsec traffic is processed over qmimux0. For the CVSS the PR:N value is appropriate because an external sender does not need a local user account when traffic can reach the affected qmimux interface. The base score uses AC:H because exploitation depends on qmi_wwan QMAP mux, a downstream MAC header consumer such as XFRM, and an affected strict alignment architecture. The paranoid score uses AC:L for deployments where those conditions are already present and incoming ESP or IPsec traffic can directly reach the interface. The demonstrated impact is availability loss only because there is no supported OOB write, UAF, information leak, or privilege escalation primitive. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 7.5 and the production ActionableScore returned 3 with recommendation Borderline / manual review recommended. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE_KPANIC because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE_KPANIC to MODERATE because the ActionableScore 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 INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS and DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 and V41_INHERITED_KPANIC_PROMOTION_BLOCKED and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 7.4 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 Borderline / manual review recommended (with actual score 3) MAYBE DANGER USB INIT NETWORK SKB KERNEL_PANIC_PLUS_UAF HARDWARE LINUS IPV6 PACKET INCREASED_TO_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 V41_INHERITED_KPANIC_PROMOTION_BLOCKED MANUAL_REVIEW_REQUIRED - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=3
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=NO
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO
1. ActionableScore
* Raw base score: 3.
* Conservative score: 3; no floor or cap applied.
* Raw paranoid score: 3.
* Paranoid score: 3; no additional technically supported primitive.
* Final recommended bucket: **Borderline / manual review recommended**::
2. Signal breakdown
* +2 Remote/net-reachable trigger: supplied evidence supports incoming IPsec traffic reaching QMAP-created raw-IP skbs without a local account in affected deployments.
* +1 Reliable kernel crash/strong DoS: the trace shows XFRM consuming the uninitialized MAC-header offset and causing an ARM alignment Oops.
* No extra availability point: it would duplicate the same crash.
* No corruption bonus: the patch shows initialization of metadata, not an OOB write, UAF, shared-backing write, or controlled overwrite.
* No integrity/confidentiality points: no disclosure or unauthorized protected-state modification is shown.
* No rarity penalty: QMAP, XFRM, and strict-alignment architecture are prerequisites, but the evidence does not establish a genuinely rare hardware-only path.
* NEW52/B5-R does not apply: there is no retry-accumulated heap OOB write or later consumption of OOB-corrupted structured state.
* V33/V34 do not apply: the attacker does not control checksum placement or the uninitialized offset value, and no non-crash cross-boundary integrity chain is shown.
3. Reachability analysis
An external sender can supply traffic to an already configured affected QMAP/IPsec path. Device and XFRM setup may require prior administrator configuration, but the packet trigger itself is below host-admin and requires neither host UID 0 nor namespace capabilities. No timing race is involved. Deployment prerequisites reduce prevalence but do not negate the demonstrated trigger.
4. Primitive and severity reading
The exact primitive is uninitialized `skb->mac_header` metadata in a raw-IP skb, later consumed by XFRM as an offset and producing a misaligned access. This is invalid active metadata with a demonstrated crash consequence, hence CLASS_C. It is not a stale-lifetime issue or proven memory-write primitive. No useful effect remains after excluding the alignment fault, so ImportantCandidate is NO and automatic Important-preservation is unwarranted.
5. One-sentence report phrase
Remote IPsec traffic over an affected QMAP interface can drive XFRM to consume an uninitialized skb MAC-header offset and crash strict-alignment ARM kernels.
6. Manual review advice
MANUAL CHECK RECOMMENDED
Confirm product exposure to qmi_wwan QMAP, IPsec/XFRM receive processing, and affected strict-alignment architectures.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup [ Upstream
Commit: d693c47fb902b988f5752182e4f7fbde5e6dcaf9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d693c47fb902b988f5752182e4f7fbde5e6dcaf9
Changed files:
drivers/net/usb/qmi_wwan.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=d693c47fb902b988f5752182e4f7fbde5e6dcaf9
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2025-68192 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2025-68192
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:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS vector: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS score: 7.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: 3
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 [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-28 14:36 21% [CVE-2025-68192][MODERATE REGULAR] net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup [ 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