From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80822: mailbox: mchp-ipc-sbi: Add null check for devm_kasprintf()
Date: Fri, 4 Sep 2026 17:27:22 +0200 [thread overview]
Message-ID: <2026090422-CVE-2026-80822-8ed4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mailbox: mchp-ipc-sbi: Add null check for devm_kasprintf()
Add a check to see if devm_kasprintf() is not NULL in
mchp_ipc_get_cluster_aggr_irq(), returning -ENOMEM if the function
failed.
The Linux kernel CVE team has assigned CVE-2026-80822 to this issue.
Affected and fixed versions
===========================
Fixed in 6.18.47 with commit 364edaedf4125825781a12c84c77699780d52a16
Fixed in 7.1.11 with commit df5c9816986b2f4d754ef3aa65a92382e9b39c4a
Fixed in 7.2.1 with commit b233e7836d98d1790e71f5f3734a86409664f341
Fixed in 7.3-rc1 with commit b37c4d0a2fd90c0c31223acd37f763eb8953ed1a
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-80822
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/mailbox/mailbox-mchp-ipc-sbi.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/364edaedf4125825781a12c84c77699780d52a16
https://git.kernel.org/stable/c/df5c9816986b2f4d754ef3aa65a92382e9b39c4a
https://git.kernel.org/stable/c/b233e7836d98d1790e71f5f3734a86409664f341
https://git.kernel.org/stable/c/b37c4d0a2fd90c0c31223acd37f763eb8953ed1a
reply other threads:[~2026-09-04 15:30 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=2026090422-CVE-2026-80822-8ed4@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.