public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Krzysztofik, Janusz" <janusz.krzysztofik@intel.com>
To: "christian.koenig@amd.com" <christian.koenig@amd.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"sumit.semwal@linaro.org" <sumit.semwal@linaro.org>
Subject: Oops: general protection fault in dma_buf_put
Date: Tue, 7 Apr 2026 11:28:26 +0000	[thread overview]
Message-ID: <68595b2ceed038074f5fe0a5739d75aafbcac8d3.camel@intel.com> (raw)

Since commit 281a226314238 ("dma-buf: add some tracepoints to qdebug.") 
we've been observing UAF reports triggered from inside dma_buf_put:

<0> [402.939643] BUG: spinlock bad magic on CPU#7, kworker/u32:5/132
<4> [402.939661] Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b759b: 0000 [#1] SMP NOPTI
<4> [402.939669] CPU: 7 UID: 0 PID: 132 Comm: kworker/u32:5 Tainted: G S   U       L   N  7.0.0-rc7-CI_DRM_18283-g0255f4a35fec+ #1 PREEMPT(lazy) 
<4> [402.939676] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [L]=SOFTLOCKUP, [N]=TEST
<4> [402.939679] Hardware name: Intel(R) Client Systems NUC11TNHi5/, BIOS TNTGL357.0042.2020.1221.1743 12/21/2020
<4> [402.939683] Workqueue: i915 __i915_gem_free_work [i915]
<4> [402.939872] RIP: 0010:spin_bug+0x77/0xe0
<4> [402.939878] Code: 83 65 8b 15 5f cf ae 02 44 8b 81 30 0a 00 00 48 81 c1 20 0d 00 00 49 83 fd ff 74 4e e8 02 67 01 00 44 8b 4b 08 4d 85 ed 74 58 <45> 8b 85 30 0a 00 00 49 8d 8d 20 0d 00 00 8b 53 04 48 89 de 48 c7
<4> [402.939885] RSP: 0018:ffffc90001557d08 EFLAGS: 00010202
<4> [402.939888] RAX: 0000000000000033 RBX: ffff8881c136b250 RCX: 0000000000000000
<4> [402.939891] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
<4> [402.939894] RBP: ffffc90001557d20 R08: 0000000000000000 R09: 000000006b6b6b6b
<4> [402.939898] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff831c6f3a
<4> [402.939901] R13: 6b6b6b6b6b6b6b6b R14: ffff888119249570 R15: ffff888108c14640
<4> [402.939904] FS:  0000000000000000(0000) GS:ffff88851c217000(0000) knlGS:0000000000000000
<4> [402.939909] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [402.939912] CR2: 00007cca7e5d7d78 CR3: 000000011c0ab001 CR4: 0000000000f72ef0
<4> [402.939915] PKRU: 55555554
<4> [402.939917] Call Trace:
<4> [402.939919]  <TASK>
<4> [402.939922]  do_raw_spin_lock+0x86/0xe0
<4> [402.939926]  _raw_spin_lock+0x37/0x60
<4> [402.939931]  ? dma_buf_put+0x30/0x120
<4> [402.939936]  dma_buf_put+0x30/0x120
<4> [402.939940]  drm_prime_gem_destroy+0x38/0x50
<4> [443.672003]  __i915_gem_free_object+0x5e/0x1d0 [i915]
...


See also https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15647.


I don't think DRM or drivers can do anything about that.  Please fix it.

Thanks,
Janusz
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
Spolka oswiadcza, ze posiada status duzego przedsiebiorcy w rozumieniu ustawy z dnia 8 marca 2013 r. o przeciwdzialaniu nadmiernym opoznieniom w transakcjach handlowych.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.

             reply	other threads:[~2026-04-07 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 11:28 Krzysztofik, Janusz [this message]
2026-04-08 12:39 ` [PATCH] dma-buf: fix UAF in dma_buf_put() tracepoint Andi Shyti
2026-04-08 12:39   ` Andi Shyti

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=68595b2ceed038074f5fe0a5739d75aafbcac8d3.camel@intel.com \
    --to=janusz.krzysztofik@intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox