From: Hanjun Guo <guohanjun@huawei.com>
To: Abbott Liu <liuwenliang@huawei.com>, <tony.luck@intel.com>,
<bp@alien8.de>, <ardb@kernel.org>, <mchehab+huawei@kernel.org>,
<rafael.j.wysocki@intel.com>, <jic23@kernel.org>,
<jason@os.amperecomputing.com>, <danielf@os.amperecomputing.com>,
<luoshengwei@huawei.com>, <linux-edac@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <yangzhuohao1@huawei.com>, <douzhaolei@huawei.com>,
<zouyipeng@huawei.com>, <wangbing6@huawei.com>,
<nixiaoming@huawei.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] RAS: Fix inverted context info bounds check in ARM processor errors
Date: Thu, 17 Sep 2026 10:13:13 +0800 [thread overview]
Message-ID: <46b53a0e-b2f8-d179-113d-0b7030e78058@huawei.com> (raw)
In-Reply-To: <20260909112832.805314-2-liuwenliang@huawei.com>
On 2026/9/9 19:28, Abbott Liu wrote:
> Commit 87880af2d24e ("APEI/GHES: ARM processor Error: don't go past
> allocated memory") added bounds checks for malformed ARM processor
> error records but contained a bug:
>
> In log_arm_hw_error(), the ctx_info bounds check is inverted. The
> condition "sz + (long)ctx_info - (long)err >= err->section_length"
> adds ctx_info->size when the context header is already past the end
> of the section instead of when it is within bounds. So change the
> comparison to <=.
>
> Fixes: 87880af2d24e ("APEI/GHES: ARM processor Error: don't go past allocated memory")
> Signed-off-by: Abbott Liu <liuwenliang@huawei.com>
> ---
> drivers/ras/ras.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/ras/ras.c b/drivers/ras/ras.c
> index 03df3db62334..2540538a16a8 100644
> --- a/drivers/ras/ras.c
> +++ b/drivers/ras/ras.c
> @@ -74,7 +74,7 @@ void log_arm_hw_error(struct cper_sec_proc_arm *err, const u8 sev)
> for (n = 0; n < err->context_info_num; n++) {
> sz = sizeof(struct cper_arm_ctx_info);
>
> - if (sz + (long)ctx_info - (long)err >= err->section_length)
> + if (sz + (long)ctx_info - (long)err <= err->section_length)
> sz += ctx_info->size;
>
> ctx_info = (struct cper_arm_ctx_info *)((long)ctx_info + sz);
>
Reviewed-by: Hanjun Guo <guohanjun@huawei.com>
Thanks
Hanjun
next prev parent reply other threads:[~2026-09-17 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 11:28 [PATCH v4 0/3] RAS: Fix ARM processor error bounds checking Abbott Liu
2026-09-09 11:28 ` [PATCH v4 1/3] RAS: Fix inverted context info bounds check in ARM processor errors Abbott Liu
2026-09-17 2:13 ` Hanjun Guo [this message]
2026-09-09 11:28 ` [PATCH v4 2/3] RAS: Fix out-of-bounds read when tracing arm_event Abbott Liu
2026-09-17 2:14 ` Hanjun Guo
2026-09-09 11:28 ` [PATCH v4 3/3] RAS: Fix integer overflow in ARM processor error context walk Abbott Liu
2026-09-21 1:29 [PATCH v4 1/3] RAS: Fix inverted context info bounds check in ARM processor errors Liuwenliang (Abbott Liu)
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=46b53a0e-b2f8-d179-113d-0b7030e78058@huawei.com \
--to=guohanjun@huawei.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=danielf@os.amperecomputing.com \
--cc=douzhaolei@huawei.com \
--cc=jason@os.amperecomputing.com \
--cc=jic23@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwenliang@huawei.com \
--cc=luoshengwei@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tony.luck@intel.com \
--cc=wangbing6@huawei.com \
--cc=yangzhuohao1@huawei.com \
--cc=zouyipeng@huawei.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
all inboxes | Powered by JetHome®