From: Jani Nikula <jani.nikula@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Hodo, Martin" <martin.hodo@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] drm/i915/hdcp: require monotonically increasing seq_num_v
Date: Mon, 29 Jun 2026 11:36:56 +0300 [thread overview]
Message-ID: <6bfadde9120c6203f01a3b29fa2a1350b5a47904@intel.com> (raw)
In-Reply-To: <DS4PPFE901A304F2E6AD5691A968A6BA2ECE3EA2@DS4PPFE901A304F.namprd11.prod.outlook.com>
On Sat, 27 Jun 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: [PATCH] drm/i915/hdcp: require monotonically increasing seq_num_v
>>
>> The HDCP 2.2 specification requires the seq_num_v to be monotonically
>> increasing, and repeated seq_num_v needs to be treated as an integrity failure.
>> Make it so.
>>
>> For the first message, seq_num_v must be zero, and is already checked. We can
>> only check for less-than-or-equal for the subsequent messages, where
>> hdcp2_encrypted is true.
>>
>> Discovered using AI-assisted static analysis confirmed by Intel Product Security.
>>
>> Reported-by: Martin Hodo <martin.hodo@intel.com>
>> Fixes: d849178e2c9e ("drm/i915: Implement HDCP2.2 repeater authentication")
>> Cc: <stable@vger.kernel.org> # v5.2+
>> Cc: Suraj Kandpal <suraj.kandpal@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> LGTM,
> Reviewed-by: Suraj Kandpal <suraj.kandpal@intel.com>
Thanks for the review, pushed to din.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/display/intel_hdcp.c | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c
>> b/drivers/gpu/drm/i915/display/intel_hdcp.c
>> index e88fec24af49..d097b478d010 100644
>> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
>> @@ -1798,9 +1798,10 @@ int hdcp2_authenticate_repeater_topology(struct
>> intel_connector *connector)
>> return -EINVAL;
>> }
>>
>> - if (seq_num_v < hdcp->seq_num_v) {
>> - /* Roll over of the seq_num_v from repeater. Reauthenticate.
>> */
>> - drm_dbg_kms(display->drm, "Seq_num_v roll over.\n");
>> + if (hdcp->hdcp2_encrypted && seq_num_v <= hdcp->seq_num_v) {
>> + /* Reauthenticate on Seq_num_v repeat or rollover */
>> + drm_dbg_kms(display->drm, "Seq_num_v %s\n",
>> + seq_num_v == hdcp->seq_num_v ? "repeat" :
>> "rollover");
>> return -EINVAL;
>> }
>>
>> --
>> 2.47.3
>
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-06-29 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 10:44 [PATCH] drm/i915/hdcp: require monotonically increasing seq_num_v Jani Nikula
2026-06-25 10:52 ` ✗ CI.checkpatch: warning for " Patchwork
2026-06-25 10:53 ` ✓ CI.KUnit: success " Patchwork
2026-06-25 11:28 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-06-25 11:36 ` ✓ i915.CI.BAT: success " Patchwork
2026-06-25 20:00 ` ✗ i915.CI.Full: failure " Patchwork
2026-06-27 4:00 ` [PATCH] " Kandpal, Suraj
2026-06-29 8:36 ` Jani Nikula [this message]
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=6bfadde9120c6203f01a3b29fa2a1350b5a47904@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=martin.hodo@intel.com \
--cc=stable@vger.kernel.org \
--cc=suraj.kandpal@intel.com \
/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.