# CVE-2026-68134: ptp: ptp_s390: Add missing facility check

> The Linux kernel PTP driver for s390 lacks a facility check, potentially causing system instability or crashes when unsupported hardware features are accessed.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68134, DEBIAN-CVE-2026-68134, GHSA-6q8g-f67g-jgcc, UBUNTU-CVE-2026-68134

## What is CVE-2026-68134?

CVE-2026-68134 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ptp: ptp_s390: Add missing facility check

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

## Which versions are affected by CVE-2026-68134?


## How do I fix CVE-2026-68134?

Apply the vendor's patch.

## Is CVE-2026-68134 being exploited?

There is no known exploitation of CVE-2026-68134 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68134 and fix it if it is affected.

What it is: CVE-2026-68134 is a high-severity vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68134 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68134/ (Markdown: https://insights.sbomify.com/CVE-2026-68134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68134
- OSV: https://osv.dev/vulnerability/CVE-2026-68134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68134/
Summaries are generated and may contain mistakes; the official description above is the record.