The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Romain Gantois" <romain.gantois@bootlin.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, "David Airlie" <airlied@gmail.com>,
	"Jason Xiang" <jx@jasonxiang.net>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
	"Paul Kocialkowski" <paulk@sys-base.io>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH v2 1/2] drm/logicvc: Avoid use-after-free with devm_kzalloc()
Date: Tue, 30 Jun 2026 12:37:53 +0000	[thread overview]
Message-ID: <b10ed22795de18c499f444e3ce8f3756@kernel.org> (raw)
In-Reply-To: <20260630-logicvc-uaf-v2-1-99e881833860@bootlin.com>

On Tue, 30 Jun 2026 11:10:10 +0200, Romain Gantois wrote:
> The logicvc driver calls drm_universal_plane_init(),
> drm_crtc_init_with_planes(), and drm_encoder_alloc(). These functions
> should not be called with structs allocated with devm_kzalloc(), as this
> can lead to use-after-free bugs. In fact, a use-after-free caused by this
> has been observed on a v6.6 kernel.
> 
> [ ... ]

Reviewed-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

  reply	other threads:[~2026-06-30 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30  9:10 [PATCH v2 0/2] drm/logicvc: Avoid UAF in DRM object management Romain Gantois
2026-06-30  9:10 ` [PATCH v2 1/2] drm/logicvc: Avoid use-after-free with devm_kzalloc() Romain Gantois
2026-06-30 12:37   ` Maxime Ripard [this message]
2026-06-30  9:10 ` [PATCH v2 2/2] drm/logicvc: Avoid using DRM resources after device is unplugged Romain Gantois
2026-06-30 12:44   ` Maxime Ripard

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=b10ed22795de18c499f444e3ce8f3756@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jx@jasonxiang.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=paulk@sys-base.io \
    --cc=romain.gantois@bootlin.com \
    --cc=simona@ffwll.ch \
    --cc=stable@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=tzimmermann@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox