From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2025-39781: parisc: Drop WARN_ON_ONCE() from flush_cache_vmap
Date: Thu, 11 Sep 2025 18:56:59 +0200 [thread overview]
Message-ID: <2025091149-CVE-2025-39781-eabe@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
parisc: Drop WARN_ON_ONCE() from flush_cache_vmap
I have observed warning to occassionally trigger.
The Linux kernel CVE team has assigned CVE-2025-39781 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.103 with commit 69cf90e5aa50fe3cb0c1a63cabc4761db44b0035
Fixed in 6.12.44 with commit 8f8a07ad04da5b3c90fab61c33d4a8256a680591
Fixed in 6.16.4 with commit 4afb1352b85d7deb777694fba16d13c30c08776f
Fixed in 6.17-rc1 with commit 4eab1c27ce1f0e89ab67b01bf1e4e4c75215708a
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-2025-39781
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:
arch/parisc/kernel/cache.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/69cf90e5aa50fe3cb0c1a63cabc4761db44b0035
https://git.kernel.org/stable/c/8f8a07ad04da5b3c90fab61c33d4a8256a680591
https://git.kernel.org/stable/c/4afb1352b85d7deb777694fba16d13c30c08776f
https://git.kernel.org/stable/c/4eab1c27ce1f0e89ab67b01bf1e4e4c75215708a
reply other threads:[~2025-09-11 16:57 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=2025091149-CVE-2025-39781-eabe@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.