From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68134: ptp: ptp_s390: Add missing facility check
Date: Mon, 10 Aug 2026 13:57:31 +0200 [thread overview]
Message-ID: <2026081058-CVE-2026-68134-641e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-68134 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 2d7de7a3010d713fb89b7ba99e6fdc14475ad106 and fixed in 6.18.42 with commit b3efb4744abf493c9782eae713b861a80d9bbeca
Issue introduced in 6.13 with commit 2d7de7a3010d713fb89b7ba99e6fdc14475ad106 and fixed in 7.1.6 with commit 545a7fdbc110c82933d448db2695abff07536f08
Issue introduced in 6.13 with commit 2d7de7a3010d713fb89b7ba99e6fdc14475ad106 and fixed in 7.2-rc5 with commit e78f1ac37afcb16cb6fef8a2c92591eab6558956
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-68134
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/ptp/ptp_s390.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b3efb4744abf493c9782eae713b861a80d9bbeca
https://git.kernel.org/stable/c/545a7fdbc110c82933d448db2695abff07536f08
https://git.kernel.org/stable/c/e78f1ac37afcb16cb6fef8a2c92591eab6558956
reply other threads:[~2026-08-10 12:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081058-CVE-2026-68134-641e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.