From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80531: xfs: avoid UAF on sc->tempip in xrep_tempfile_create
Date: Wed, 26 Aug 2026 16:37:27 +0200 [thread overview]
Message-ID: <2026082603-CVE-2026-80531-36dd@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xfs: avoid UAF on sc->tempip in xrep_tempfile_create
LOLLM noticed a potential UAF if the tempfile creation code fails after
it set sc->tempip. Fix that.
The Linux kernel CVE team has assigned CVE-2026-80531 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 84c14ee39dd388d73054181c70b3f42af7ddc238 and fixed in 6.12.105 with commit 08a20776ce33a2a52d856911e447c59424f0465a
Issue introduced in 6.10 with commit 84c14ee39dd388d73054181c70b3f42af7ddc238 and fixed in 6.18.46 with commit cd1f876d1bc2e94f271e07c606cacd85b109108a
Issue introduced in 6.10 with commit 84c14ee39dd388d73054181c70b3f42af7ddc238 and fixed in 7.1.10 with commit 96246a3200d32a43766152e56bc7ae2d93604d74
Issue introduced in 6.10 with commit 84c14ee39dd388d73054181c70b3f42af7ddc238 and fixed in 7.2 with commit 0c88e10d12de9ca7cbed1467bb1b52310101bff8
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-80531
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/xfs/scrub/tempfile.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/08a20776ce33a2a52d856911e447c59424f0465a
https://git.kernel.org/stable/c/cd1f876d1bc2e94f271e07c606cacd85b109108a
https://git.kernel.org/stable/c/96246a3200d32a43766152e56bc7ae2d93604d74
https://git.kernel.org/stable/c/0c88e10d12de9ca7cbed1467bb1b52310101bff8
reply other threads:[~2026-08-26 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026082603-CVE-2026-80531-36dd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--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.