Re: [PATCH net] tipc: protect received keys from concurrent flush
From: Jérémy Jean
Date: Fri Oct 02 2026 - 09:00:51 EST
On 2026-10-02 14:50, Tung Quang Nguyen wrote:
[ 12.986077] BUG: KASAN: double-free inPlease update your changelog with decoded stack trace.
tipc_crypto_key_flush+0x401/0x530
[ 12.987937] Free of addr ff11000002268080 by task peer/112
...
[ 12.991938] kfree+0x163/0x430
...
[ 12.991983] tipc_crypto_key_flush+0x401/0x530
...
[ 12.992152] tipc_nl_node_flush_key+0x174/0x210
You mean the full trace including the parts I snipped?
A full stack trace would help me track back the calling flow. Of course, your need to decode (e.g, +0x174/0x210 to line number etc.) the stack trace using:
linux/scripts/decode_stacktrace.sh
Thanks for this advice, I never used that but will tkae a look.
Do you have a reproducer ?
Yes, I have.
Please share it to me. It could be good to run and observe if there is another stack trace based on different conditions (other concurrencies etc.)
No problem, I will do that shortly.
Regards,
Jérémy