From: syzbot <syzbot+901d48e0b95aed4a2548@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Re: [syzbot] [net?] memory leak in xfrm_policy_construct
Date: Fri, 17 Apr 2026 06:37:19 -0700 [thread overview]
Message-ID: <69e2378f.a00a0220.1bd0ca.0003.GAE@google.com> (raw)
In-Reply-To: <69d678c4.050a0220.3030df.000a.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [net?] memory leak in xfrm_policy_construct
Author: nogikh@google.com
Hi Helen,
Thanks for looking into the issue!
Nit: it's better to directly Cc original syzbot emails
(syzbot+901d48e0b95aed4a2548@syzkaller.appspotmail.com in this case)
when sending commands to it, otherwise it may not recognize the bug.
#syz fix: xfrm: fix refcount leak in xfrm_migrate_policy_find
--
Aleksandr
On Fri, Apr 17, 2026 at 3:32 PM Helen Koike <koike@igalia.com> wrote:
>
> Hey all,
>
> I just noticed I couldn't reproduce on 7.0 upstream/master (3cd8b194bf34), and from a bisect I found that commit 83317cce60a0 "xfrm: fix refcount leak in xfrm_migrate_policy_find" fixes this issue. Which is clear by the commit message and I also reverted it on upstream/master and validated it reproduces. So I'm marking it as fixed:
>
> #syz fix: "xfrm: fix refcount leak in xfrm_migrate_policy_find"
>
> Em sábado, 11 de abril de 2026 às 22:27:03 UTC-3, syzbot escreveu:
>>
>> Hello,
>>
>> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>>
>> Reported-by: syzbot+901d48...@syzkaller.appspotmail.com
>> Tested-by: syzbot+901d48...@syzkaller.appspotmail.com
>>
>> Tested on:
>>
>> commit: f5459048 Merge tag 'i2c-for-7.0-final' of git://git.ke..
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12b8f302580000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=e2bba615ee79faa5
>> dashboard link: https://syzkaller.appspot.com/bug?extid=901d48e0b95aed4a2548
>> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
>> patch: https://syzkaller.appspot.com/x/patch.diff?x=14e2c74e580000
>>
>> Note: testing is done by a robot and is best-effort only.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/8b891373-c70d-4fa9-b8b1-8c1fa06e0756n%40googlegroups.com.
prev parent reply other threads:[~2026-04-17 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 15:48 [syzbot] [net?] memory leak in xfrm_policy_construct syzbot
2026-04-12 0:23 ` Forwarded: [PATCH] xfrm: fix memory leak and improper cleanup in xfrm_add_policy() syzbot
2026-04-17 13:37 ` syzbot [this message]
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=69e2378f.a00a0220.1bd0ca.0003.GAE@google.com \
--to=syzbot+901d48e0b95aed4a2548@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.