From: Greg KH <gregkh@linuxfoundation.org>
To: Matthias Merz <linux@merz-ka.de>
Cc: stable@vger.kernel.org, Dong Chenchen <dongchenchen2@huawei.com>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [6.12.y] Please backport 8045c0df98d4 ("xfrm: Fix dev use-after-free in xfrm async resumption")
Date: Fri, 7 Aug 2026 16:44:59 +0200 [thread overview]
Message-ID: <2026080738-eastward-nimbly-e78d@gregkh> (raw)
In-Reply-To: <anXqAxQBTgPtQSXT@C-25H12I214949.jacob.local>
On Fri, Aug 07, 2026 at 04:21:55PM +0200, Matthias Merz wrote:
> Hello,
>
> Please apply upstream commit 8045c0df98d4 ("xfrm: Fix dev use-after-free
> in xfrm async resumption") also to 6.12.y. Stable 7.1.5 contains this in
> 63a300151999.
>
> It fixes 1c428b038400 ("xfrm: hold dev ref until after transport_finish
> NF_HOOK"), which is present in 6.12.y since 6.12.94. On our IPsec
> gateways using xfrm interfaces this issue underflows the interface
> refcount and hangs unregister_netdevice() on tunnel teardown, rekey or
> system shutdown:
>
> unregister_netdevice: waiting for xfrm-<ifname> to become free. Usage count = -381
>
> This leads to a complete drop of our VPN links after some hours, and
> stalls the reboot for a couple of minutes waiting for devices to become
> free (I remember waiting 10-15 minutes for the shutdown when remote
> rebooting a gateway without physical access)
>
> known affected: 6.12.96 and 6.12.96, known unaffected 6.12.90
> Fixed in 7.1.5 via 63a300151999.
It does not apply cleanly to those trees, please provide a working
backport that you have tested and we will be glad to apply it.
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-07 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 14:21 [6.12.y] Please backport 8045c0df98d4 ("xfrm: Fix dev use-after-free in xfrm async resumption") Matthias Merz
2026-08-07 14:44 ` Greg KH [this message]
2026-08-20 12:18 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2026-09-23 7:53 Kusuma DS
2026-09-23 9:31 ` Greg KH
2026-09-23 9:56 ` Kusuma DS
2026-09-23 10:27 ` Greg KH
2026-09-25 18:48 ` Sasha Levin
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=2026080738-eastward-nimbly-e78d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dongchenchen2@huawei.com \
--cc=linux@merz-ka.de \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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.