[CVE-2026-68134][MODERATE REGULAR] ptp: ptp_s390: Add missing facility check

[CVE-2026-68134][MODERATE REGULAR] ptp: ptp_s390: Add missing facility check

[AL-KERNEL]

CVE: CVE-2026-68134
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: ptp: ptp_s390: Add missing facility check
Commit: b3efb4744abf493c9782eae713b861a80d9bbeca
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b3efb4744abf493c9782eae713b861a80d9bbeca
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68134
Analysis date: Mon, 10 Aug 2026 13:45:06 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
The s390 PTP driver could register a QPT clock without verifying facility 28 and PTFF_QPT availability, allowing local userspace that can access the PTP device to trigger failed operations or a possible local DoS on affected s390 systems.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68134 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68134

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-68134	MODERATE	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-754;CWE-703;CWE-665;Other CVSS 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'The s390 PTP driver could register the QPT physical clock even when facility 28 is not installed or PTFF_QPT is not reported as available. This exposes a PTP clock backed by an unsupported hardware function, so local userspace that can access the PTP device may hit warnings, failed operations, or a kernel fault depending on the s390 environment. For the CVSS the PR:L is used because reliable triggering generally requires local code execution and access to the registered PTP device, but not full administrative privileges once the driver is present. The issue is not network reachable. Impact is mainly denial of service or device malfunction, with no supported path to information disclosure or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)  SKIP CVE-2026-68134 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 2d7de7a3010d YES  NO NO unknown 	MAYBE	INIT SIMPLEFIX LINUS 	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

Conservative signals:

* +1 Availability impact realistic: registering a QPT PTP clock without checking facility 28 and PTFF_QPT availability can expose an unsupported clock device and cause failed operations or device malfunction.
* +1 Local trigger possible: once the clock device is registered, local userspace with access to the PTP device may be able to exercise the broken path.
* -1 Rare hardware/configuration exposure: this is specific to s390 PTP support and systems lacking the required facility or PTFF_QPT capability.

Paranoid additional signal:

* +1 Reliable kernel crash / strong DoS concern: if the unsupported QPT operation reaches a faulting hardware instruction path, a kernel fault or oops is plausible, but the patch does not show memory corruption or a demonstrated crash path.

Signals not awarded:

* No remote/network reachability.
* No firmware-mediated attacker influence.
* No UAF, double-free, OOB write, type confusion, refcount takeover, or arbitrary write.
* No privilege escalation evidence.
* No confidentiality or integrity impact supported by the patch.

Call-site confidence: medium. The init and exit paths are shown, but the exact ptp_qpt_clock operation call sites are not included in the provided patch.

## 3. Reachability analysis

The issue is local and hardware/configuration dependent. It affects s390 systems where the ptp_s390 driver is present and the required facility 28 or PTFF_QPT support is unavailable, yet the driver still registers the QPT clock. Triggering likely requires local userspace access to the registered PTP device. Containers or namespaces do not obviously improve reachability unless the PTP device is explicitly exposed into the container. The path is not network reachable and is not a common default exposure outside affected s390 environments.

## 4. Severity interpretation

This behaves more like an ordinary Moderate or Low-like hardware capability validation issue than an Important-class kernel vulnerability. The realistic impact is device malfunction or local DoS. The paranoid interpretation allows for a kernel fault if unsupported QPT operations are reached, but there is no evidence of memory corruption, privilege escalation, information disclosure, or cross-boundary policy bypass.

## 5. One-sentence report phrase

The s390 PTP driver could register a QPT clock without verifying facility 28 and PTFF_QPT availability, allowing local userspace that can access the PTP device to trigger failed operations or a possible local DoS on affected s390 systems.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This should not be auto-escalated to Important based on the provided patch. Manual review is only useful if the product has significant s390 exposure and evidence that unsupported QPT operations reliably cause a host-wide kernel crash.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: ptp: ptp_s390: Add missing facility check
Commit: b3efb4744abf493c9782eae713b861a80d9bbeca
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b3efb4744abf493c9782eae713b861a80d9bbeca

Commit description:

Only register the physical clock when facility 28 is installed
and PTFF QAF returns that PTFF QPT is available.

Fixes: 2d7de7a ("s390/time: Add PtP driver")
Signed-off-by: Sven Schnelle <svens@linux.ibm.com>
Cc: stable@kernel.org
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Link: https://patch.msgid.link/20260714130342.1971700-3-svens@linux.ibm.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/ptp/ptp_s390.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=b3efb4744abf493c9782eae713b861a80d9bbeca

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68134 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68134

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: 1
  Paranoid ActionableScore: 2

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).