From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46016: remoteproc: xlnx: Only access buffer information if IPI is buffered
Date: Wed, 27 May 2026 14:59:07 +0200 [thread overview]
Message-ID: <2026052745-CVE-2026-46016-e12d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: xlnx: Only access buffer information if IPI is buffered
In the receive callback check if message is NULL to prevent
possibility of crash by NULL pointer dereferencing.
The Linux kernel CVE team has assigned CVE-2026-46016 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.4 with commit 5dfb28c257b7c515624ba6b163410ceada451bf2 and fixed in 6.6.140 with commit 5d1451cb2cf6f3d9884d76035a1460aa9bb4b053
Issue introduced in 6.4 with commit 5dfb28c257b7c515624ba6b163410ceada451bf2 and fixed in 6.12.86 with commit 7ddbf21116770b7011f2bb0a6056b7604b24c497
Issue introduced in 6.4 with commit 5dfb28c257b7c515624ba6b163410ceada451bf2 and fixed in 6.18.27 with commit 06d0bed2552fd0dae27d374d4492a2b672e24eed
Issue introduced in 6.4 with commit 5dfb28c257b7c515624ba6b163410ceada451bf2 and fixed in 7.0.4 with commit 8242579859a78c801bb626e9aa4823aca93e28e7
Issue introduced in 6.4 with commit 5dfb28c257b7c515624ba6b163410ceada451bf2 and fixed in 7.1-rc1 with commit 38dd6ccfdfbbe865569a52fe1ba9fa1478f672e6
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-46016
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:
drivers/remoteproc/xlnx_r5_remoteproc.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/5d1451cb2cf6f3d9884d76035a1460aa9bb4b053
https://git.kernel.org/stable/c/7ddbf21116770b7011f2bb0a6056b7604b24c497
https://git.kernel.org/stable/c/06d0bed2552fd0dae27d374d4492a2b672e24eed
https://git.kernel.org/stable/c/8242579859a78c801bb626e9aa4823aca93e28e7
https://git.kernel.org/stable/c/38dd6ccfdfbbe865569a52fe1ba9fa1478f672e6
reply other threads:[~2026-05-27 13:03 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=2026052745-CVE-2026-46016-e12d@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.