Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Amelia Crate <acrate@waldn.net>
Cc: stable@vger.kernel.org, dimitri.ledkov@surgut.co.uk
Subject: Re: [PATCH 0/4] Backport CVE fixes to 6.12.y
Date: Thu, 30 Oct 2025 06:26:24 +0100	[thread overview]
Message-ID: <2025103043-refinish-preformed-280e@gregkh> (raw)
In-Reply-To: <79b19099-3791-4690-8729-de15128d79b7@waldn.net>

On Wed, Oct 29, 2025 at 05:24:59PM -0500, Amelia Crate wrote:
> These patches backport the following upstream commits fixing CVEs to the Linux 6.12.y stable tree.
> 
> CVE-2025-21833 -> 60f030f7418d ("iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE")
> CVE-2025-37803 -> 021ba7f1babd ("udmabuf: fix a buf size overflow issue during udmabuf creation")
> CVE-2024-57995 -> 5a10971c7645 ("wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev()")
> CVE-2025-37860 -> 8241ecec1cdc6 ("sfc: fix NULL dereferences in ef100_process_design_param()")
> 
> The following upstream commit applies cleanly to v6.12.y, please pick it up.
> 
> CVE-2024-58097 -> 16c6c35c03ea ("wifi: ath11k: fix RCU stall while reaping monitor destination ring")
> 
> 
> 

All of these seem to be attached (with full git headers?) and the
whitespace is corrupted and can not be applied at all :(

Can you resend these using something like git send-email which will fix
all of that up properly?

thanks,

greg k-h

  parent reply	other threads:[~2025-10-30  5:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 22:24 [PATCH 0/4] Backport CVE fixes to 6.12.y Amelia Crate
2025-10-29 22:25 ` [PATCH 1/4] iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE Amelia Crate
2025-10-29 22:26   ` [PATCH 2/4] udmabuf: fix a buf size overflow issue during udmabuf creation Amelia Crate
2025-10-29 22:27     ` [PATCH 3/4] wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() Amelia Crate
2025-10-29 22:27       ` [PATCH 4/4] sfc: fix NULL dereferences in ef100_process_design_param() Amelia Crate
2025-10-30  5:26 ` Greg KH [this message]
2025-10-30 16:08   ` [PATCH v2 0/4] Backport CVE fixes to 6.12.y Amelia Crate
2025-10-30 16:08     ` [PATCH v2 1/4] iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE Amelia Crate
2025-10-30 16:08     ` [PATCH v2 2/4] udmabuf: fix a buf size overflow issue during udmabuf creation Amelia Crate
2025-10-30 16:08     ` [PATCH v2 3/4] wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() Amelia Crate
2025-10-30 16:08     ` [PATCH v2 4/4] sfc: fix NULL dereferences in ef100_process_design_param() Amelia Crate

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=2025103043-refinish-preformed-280e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=acrate@waldn.net \
    --cc=dimitri.ledkov@surgut.co.uk \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox