From: Ira Weiny <ira.weiny@intel.com>
To: Dan Carpenter <dan.carpenter@linaro.org>,
Zaid Alali <zaidal@os.amperecomputing.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, "Borislav Petkov" <bp@alien8.de>,
Ira Weiny <ira.weiny@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Al Viro <viro@zeniv.linux.org.uk>,
"Sudeep Holla" <sudeep.holla@arm.com>,
Jon Hunter <jonathanh@nvidia.com>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH next] ACPI: APEI: EINJ: prevent memory corruption in error_type_set()
Date: Wed, 25 Jun 2025 16:21:09 -0500 [thread overview]
Message-ID: <685c684533e1c_2c354429441@iweiny-mobl.notmuch> (raw)
In-Reply-To: <ae6286cf-4d73-4b97-8c0f-0782a65b8f51@sabinyo.mountain>
Dan Carpenter wrote:
> The "einj_buf" buffer is 32 chars. If "count" is larger than that it
> results in memory corruption. Cap it at 31 so that we leave the last
> character as a NUL terminator. By the way, the highest reasonable value
> for "count" is 24.
>
> Fixes: 0c6176e1e186 ("ACPI: APEI: EINJ: Enable the discovery of EINJv2 capabilities")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
[snip]
next prev parent reply other threads:[~2025-06-25 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 18:57 [PATCH next] ACPI: APEI: EINJ: prevent memory corruption in error_type_set() Dan Carpenter
2025-06-25 21:21 ` Ira Weiny [this message]
2025-06-26 18:47 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2025-06-25 15:23 Dan Carpenter
2025-06-25 15:58 ` Dan Carpenter
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=685c684533e1c_2c354429441@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bp@alien8.de \
--cc=dan.carpenter@linaro.org \
--cc=james.morse@arm.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zaidal@os.amperecomputing.com \
/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