[PATCH v1 RFC] video/hdmi: Fix HDMI_VENDOR_INFOFRAME_SIZE
Martin Blumenstingl
martin.blumenstingl at googlemail.com
Sat Feb 11 20:43:50 UTC 2023
Hello Ville.
On Mon, Feb 6, 2023 at 10:58 AM Ville Syrjälä
<ville.syrjala at linux.intel.com> wrote:
[...]
> > Change HDMI_VENDOR_INFOFRAME_SIZE to 6 bytes so
> > hdmi_vendor_infoframe_pack_only() can properly check the passed buffer
> > size and avoid an out of bounds write to ptr[8] or ptr[9].
>
> The function should return -ENOSPC if the caller didn't
> provide a big enough buffer.
Indeed, I'm not sure why I didn't notice when I sent the patch.
> Are you saying there are drivers that are passing a bogus size here?
Thankfully not - at least when I checked the last time drivers passed
a 10 byte - or bigger - buffer.
My main concern is the HDMI_INFOFRAME_SIZE macro. It's used in various
drivers like this:
u8 buffer[HDMI_INFOFRAME_SIZE(AVI)];
One could use HDMI_VENDOR_INFOFRAME_SIZE with this as well:
u8 buffer[HDMI_INFOFRAME_SIZE(VENDOR)];
But it would only result in an 8 byte wide buffer.
Nobody uses it like this yet.
Do you see any reason why my patch could cause problems?
If not then I want to re-send it with an updated description.
Best regards,
Martin
More information about the dri-devel
mailing list