[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87ms1z6luq.fsf@intel.com>
Date: Tue, 27 Jan 2026 08:50:37 -0800
From: Vinicius Costa Gomes <vinicius.gomes@...el.com>
To: Daniel J Blueman <daniel@...ra.org>, dmaengine@...r.kernel.org,
linux-kernel@...r.kernel.org, Vinod Koul <vkoul@...nel.org>, Dave Jiang
<dave.jiang@...el.com>
Cc: Daniel J Blueman <daniel@...ra.org>, Scott Hamilton
<scott.hamilton@...den.com>, stable@...r.kernel.org
Subject: Re: [PATCH] idxd: Fix Intel Data Streaming Accelerator double-free
on error path
Hi Daniel,
Daniel J Blueman <daniel@...ra.org> writes:
> During IDXD driver probe unwind from an earlier resource allocation
> failure, multiple use-after-free codepaths are taken leading to attempted
> double-free of ID allocator entries and memory allocations, eg:
>
> ida_free called for id=64 which is not allocated.
> WARNING: lib/idr.c:594 at ida_free+0x1af/0x1f4, CPU#900: kworker/900:1/11863
> ...
> Call Trace:
> <TASK>
> ? ida_destroy+0x258/0x258
> idxd_pci_probe_alloc+0x342e/0x348c
> ? multi_u64_to_bmap+0xc9/0xc9
> ? queued_read_unlock+0x1e/0x1e
> ? __schedule+0x2e43/0x2ee6
> ? idxd_reset_done+0x12ca/0x12ca
> idxd_pci_probe+0x15/0x17
> ...
>
> Fix this by releasing these allocations only after use and once.
>
> Validated on 8 socket and 16 socket (XNC node controller) Intel Saphire
> Rapids XCC systems with no KASAN, Kmemleak or lockdep reports.
Can you confirm that you still see this issue after you apply the series
I sent last week?
Cheers,
--
Vinicius
Powered by blists - more mailing lists