Netdev List
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	Tahera Fahimi <taherafahimi@linux.microsoft.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org
Subject: Re: Backport xfrm race condition fix to stable kernel version 6.6.y
Date: Tue, 18 Aug 2026 23:32:28 -0400	[thread overview]
Message-ID: <20260818220420.14@kernel.org> (raw)
In-Reply-To: <20260817221108.778584-2-taherafahimi@linux.microsoft.com>

On Mon, Aug 17, 2026 at 03:10:09PM -0700, Tahera Fahimi wrote:
> I am writing to request the backport of the following patch to stable kernel versions 6.6.y,
> addressing CVE-2026-31516.
>
> Patch to Apply:
>     Subject: xfrm: prevent policy_hthresh.work from racing with netns teardown
>     Commit ID: 29fe3a61bcdce398ee3955101c39f89c01a8a77e

This one is already in 7.1.y, 6.18.y and 6.12.y, but it can't be taken
as-is on 6.6 and older: the line it adds calls disable_work_sync(), which
only exists from v6.10 onwards, 86898fa6b8cd ("workqueue: Implement
disable/enable for (delayed) work items"). The cherry-pick applies
cleanly and then fails to build.

Substituting cancel_work_sync() compiles, but it drops the re-queue
prevention the commit exists to add, and I'd rather not make that
substitution silently on a CVE fix.

Could you send a tested backport for the pre-6.10 trees (6.6, 6.1, 5.15,
5.10)? Netdev folks Cc'd in case they'd rather do it.

-- 
Thanks,
Sasha

           reply	other threads:[~2026-08-19  3:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260817221108.778584-2-taherafahimi@linux.microsoft.com>]

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=20260818220420.14@kernel.org \
    --to=sashal@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=taherafahimi@linux.microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox