Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-misc-fixes
Date: Fri, 29 May 2026 09:00:09 +0200	[thread overview]
Message-ID: <20260529070009.GA313534@linux.fritz.box> (raw)

Hi Dave, Sima,

here is this week's PR from drm-misc-fixes. There's one cross-subsys
commit to the dma-buf code. Commit 5ab62dd3687b ("drm: prevent integer
overflows in dumb buffer creation helpers") has not Link tag because
it went through the security list.

Best regards
Thomas

drm-misc-fixes-2026-05-29:
Short summary of fixes pull:

amdxdna:
- require IOMMU on AIE2

dumb-buffer:
- prevent overflows in dumb-buffer creation

dma-buf:
- fix UAF in dma_buf_fd() tracepoint

hyperv:
- improve protocol validation

ivpu:
- test write offset in debugfs

rocket:
- fix UAF in bo creation
The following changes since commit 9af1b6e175c82daf4b423da339a722d8e67a735a:

  drm/virtio: use uninterruptible resv lock for plane updates (2026-05-20 18:12:11 +0300)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/misc/kernel.git tags/drm-misc-fixes-2026-05-29

for you to fetch changes up to 5ab62dd3687bcc2cc542b99385aabac5c996db6f:

  drm: prevent integer overflows in dumb buffer creation helpers (2026-05-29 08:30:47 +0200)

----------------------------------------------------------------
Short summary of fixes pull:

amdxdna:
- require IOMMU on AIE2

dumb-buffer:
- prevent overflows in dumb-buffer creation

dma-buf:
- fix UAF in dma_buf_fd() tracepoint

hyperv:
- improve protocol validation

ivpu:
- test write offset in debugfs

rocket:
- fix UAF in bo creation

----------------------------------------------------------------
Berkant Koc (2):
      drm/hyperv: validate resolution_count and fix WIN8 fallback
      drm/hyperv: validate VMBus packet size in receive callback

Dan Carpenter (1):
      accel/ivpu: prevent uninitialized data bug in debugfs

David Carlier (1):
      dma-buf: fix UAF in dma_buf_fd() tracepoint

Dhabaleshwar Das (1):
      accel/rocket: fix UAF via dangling GEM handle in create_bo

Lizhi Hou (1):
      accel/amdxdna: Block running when IOMMU is off

Rajat Gupta (1):
      drm: prevent integer overflows in dumb buffer creation helpers

 drivers/accel/amdxdna/aie2_pci.c          |   5 ++
 drivers/accel/ivpu/ivpu_debugfs.c         |   2 +-
 drivers/accel/rocket/rocket_gem.c         |  17 +++--
 drivers/dma-buf/dma-buf.c                 |   6 +-
 drivers/gpu/drm/drm_dumb_buffers.c        |  14 +++-
 drivers/gpu/drm/hyperv/hyperv_drm_proto.c | 113 +++++++++++++++++++++++++-----
 6 files changed, 132 insertions(+), 25 deletions(-)

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)

             reply	other threads:[~2026-05-29  7:00 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  7:00 Thomas Zimmermann [this message]
2026-06-01 15:28 ` [PULL] drm-misc-fixes Jani Nikula
2026-06-01 15:38   ` Jani Nikula
2026-06-01 15:49     ` Jani Nikula
2026-06-01 17:26       ` Thomas Zimmermann
2026-06-01 19:23         ` Saarinen, Jani
2026-06-02  7:01           ` Saarinen, Jani
2026-06-01 19:52         ` Jani Nikula
2026-06-02  6:36           ` Thomas Zimmermann
2026-06-02  8:02   ` Thomas Zimmermann
  -- strict thread matches above, loose matches on Subject: below --
2026-06-05  7:26 Thomas Zimmermann
2026-05-21  7:14 Thomas Zimmermann
2026-05-15  7:08 Thomas Zimmermann
2026-05-07 11:52 Thomas Zimmermann
2026-04-30  6:45 Thomas Zimmermann
2026-04-23  5:41 Maxime Ripard
2026-04-09  8:15 Maxime Ripard
2026-04-02  7:52 Maxime Ripard
2026-03-26  7:17 Maxime Ripard
2026-03-19  7:20 Maxime Ripard
2026-03-12  7:30 Maxime Ripard
2026-03-06  6:41 Maxime Ripard
2026-03-05  8:09 Maxime Ripard
2026-02-26  8:36 Maxime Ripard
2026-02-05  9:53 Maarten Lankhorst
2026-01-29 17:01 Maarten Lankhorst
2026-01-22  9:50 Maarten Lankhorst
2026-01-16 11:46 Maarten Lankhorst
2026-01-07  9:45 Maarten Lankhorst
2025-12-30 19:40 Maarten Lankhorst
2025-12-18 10:05 Maarten Lankhorst
2025-12-10 11:29 Maarten Lankhorst
2025-11-27  8:10 Thomas Zimmermann
2025-11-20 15:13 Thomas Zimmermann
2025-11-13 13:23 Thomas Zimmermann
2025-11-06 13:12 Thomas Zimmermann
2025-10-30 19:56 Thomas Zimmermann
2025-10-31 18:10 ` Simona Vetter
2025-10-23  8:34 Thomas Zimmermann
2025-10-24 11:36 ` Simona Vetter
2025-10-16 14:16 Thomas Zimmermann
2025-10-09 12:00 Thomas Zimmermann
2025-09-25 11:32 Maxime Ripard
2025-09-18  8:24 Maxime Ripard
2025-09-11 16:04 Maxime Ripard
2025-09-03  7:57 Maxime Ripard
2025-08-28  6:32 Maxime Ripard
2025-08-21  8:12 Maxime Ripard
2025-07-23  9:18 Maarten Lankhorst
2025-07-16  7:42 Maarten Lankhorst
2025-07-10  8:59 Maarten Lankhorst
2025-07-11 12:15 ` Simona Vetter
2025-07-03 15:26 Maarten Lankhorst
2025-06-27  7:04 Maarten Lankhorst
2025-06-19  8:12 Maarten Lankhorst
2025-06-12 11:53 Maarten Lankhorst
2025-06-06  7:28 Thomas Zimmermann
2025-06-06 13:03 ` Simona Vetter
2025-05-28 15:35 Thomas Zimmermann
2025-06-06 12:38 ` Simona Vetter
2025-05-22 11:49 Thomas Zimmermann
2025-05-15 12:55 Thomas Zimmermann
2025-05-08 10:49 Thomas Zimmermann
2025-04-30  8:24 Maxime Ripard
2025-04-22 15:12 Thomas Zimmermann
2025-04-17  8:40 Thomas Zimmermann
2025-04-10 12:24 Thomas Zimmermann
2025-03-20  8:38 Maxime Ripard
2025-03-13  7:36 Maxime Ripard
2025-03-06 10:32 Maxime Ripard
2025-02-27 14:10 Maxime Ripard
2025-02-20  8:30 Maxime Ripard
2025-02-13 15:30 Maxime Ripard
2025-02-06  9:15 Maxime Ripard
2025-01-24  8:29 Thomas Zimmermann
2025-01-24 10:42 ` Simona Vetter
2025-01-15  9:22 Maarten Lankhorst
2025-01-02  8:47 Maarten Lankhorst
2024-12-19 18:10 Maarten Lankhorst
2024-12-05 19:48 Maarten Lankhorst
2024-11-28 13:59 Thomas Zimmermann
2024-11-21 13:18 Thomas Zimmermann
2024-11-14 14:22 Thomas Zimmermann
2024-11-08  8:50 Thomas Zimmermann
2024-10-31 14:43 Thomas Zimmermann
2024-10-24 12:49 Thomas Zimmermann
2024-10-17 11:55 Thomas Zimmermann
2024-10-10 13:37 Thomas Zimmermann
2024-10-02 15:15 Thomas Zimmermann
2024-09-26 12:10 Thomas Zimmermann
2024-09-12  8:49 Maxime Ripard
2024-09-05 14:19 Maxime Ripard
2024-08-29 14:51 Maxime Ripard
2024-08-22 12:39 Thomas Zimmermann
2024-08-15 13:17 Thomas Zimmermann
2024-08-08  7:48 Maxime Ripard
2024-08-01  9:00 Maxime Ripard
2024-07-11  9:51 Maarten Lankhorst
2024-07-04 12:27 Maarten Lankhorst
2024-07-04 14:49 ` Daniel Vetter
2024-06-26 15:35 Maarten Lankhorst
2024-06-14  8:13 Maarten Lankhorst
2024-06-06 22:09 Maarten Lankhorst
2024-05-30 19:23 Thomas Zimmermann
2024-05-23 18:47 Thomas Zimmermann
2024-05-16  7:26 Thomas Zimmermann
2024-05-10  7:20 Thomas Zimmermann
2024-05-02 19:21 Thomas Zimmermann
2024-04-25 10:24 Thomas Zimmermann
2024-04-18  7:22 Thomas Zimmermann
2024-04-11  7:34 Thomas Zimmermann
2024-04-04 10:48 Thomas Zimmermann
2024-03-28 13:44 Thomas Zimmermann
2024-03-07  8:44 Maxime Ripard
2024-02-29 13:37 Maxime Ripard
2024-02-29 13:54 ` Matthew Auld
2024-03-06 14:26   ` 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=20260529070009.GA313534@linux.fritz.box \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.brost@intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    /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