From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74603: ptp: ocp: Fix board ID over-read
Date: Sat, 22 Aug 2026 17:31:27 +0200 [thread overview]
Message-ID: <2026082215-CVE-2026-74603-955f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ptp: ocp: Fix board ID over-read
The EEPROM board ID is a fixed 13-byte field and is not guaranteed to
contain a NUL terminator. Passing it directly to
devlink_info_version_fixed_put() treats it as a C string and may read
beyond the field.
Format at most OCP_BOARD_ID_LEN bytes into the existing local buffer
before reporting the ID. Use a precision limit because the snprintf()
output size alone does not bound the source string scan.
The Linux kernel CVE team has assigned CVE-2026-74603 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 6.1.183 with commit 72ef3ce80078199bfad32f98d055f44ba7cd0c3d
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 6.6.152 with commit 3d965811be78473654e6e8cc8e4fb7b6b87aa6c1
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 6.12.104 with commit f92558bbe78d6284fedd053900f82a70f0aa8707
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 6.18.45 with commit 5fd91dd4a143479b0575fb1f202ec1c501e71fd5
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 7.1.9 with commit f8d7e5751267637190eff887c971d5b468106213
Issue introduced in 5.18 with commit 0cfcdd1ebcfe1a9b262f6ad8419580720dc843c4 and fixed in 7.2 with commit 6b69f2ef10cdb018c0b127a7cab88e590bbddba4
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-74603
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_ocp.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/72ef3ce80078199bfad32f98d055f44ba7cd0c3d
https://git.kernel.org/stable/c/3d965811be78473654e6e8cc8e4fb7b6b87aa6c1
https://git.kernel.org/stable/c/f92558bbe78d6284fedd053900f82a70f0aa8707
https://git.kernel.org/stable/c/5fd91dd4a143479b0575fb1f202ec1c501e71fd5
https://git.kernel.org/stable/c/f8d7e5751267637190eff887c971d5b468106213
https://git.kernel.org/stable/c/6b69f2ef10cdb018c0b127a7cab88e590bbddba4
reply other threads:[~2026-08-22 15:34 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=2026082215-CVE-2026-74603-955f@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.