All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liuwenliang (Abbott Liu)" <liuwenliang@huawei.com>
To: "Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
	"tony.luck@intel.com" <tony.luck@intel.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
	"mchehab+huawei@kernel.org" <mchehab+huawei@kernel.org>,
	"ardb@kernel.org" <ardb@kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "yangzhuohao (A)" <yangzhuohao1@huawei.com>,
	douzhaolei <douzhaolei@huawei.com>,
	zouyipeng <zouyipeng@huawei.com>, Wangbing <wangbing6@huawei.com>,
	Nixiaoming <nixiaoming@huawei.com>,
	"Liuwenliang (Abbott Liu)" <liuwenliang@huawei.com>
Subject: Re: [PATCH] RAS: Fix out-of-range section_length in ARM processor error handling
Date: Tue, 25 Aug 2026 12:21:47 +0000	[thread overview]
Message-ID: <fff991d1207b4548be577ea65e27bc10@huawei.com> (raw)

Hi Hanjun, thanks for your review.
>Hi Abbott,
>
>On 2026/8/20 21:18, 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 several bugs:
>> 
>> - 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 <=.
>> 
>> - The vsei_len < 0 error path did not verify the pei_len and ctx_len.
>>    When vsei_len is negative, section_length is too small to hold the
>>    full record, yet pei_len and ctx_len were derived from
>>    err_info_num/context_info_num and may describe regions beyond the
>>    (long)err .. err + section_length buffer. To prevent trace_arm_event
>>    from reading past the allocated record, sanitize the parameters:
>>    move the cpu lookup above this path so it is available for tracing,
>>    recalculate ctx_len and pei_len based on section_length, limit them,
>>    set the corresponding pointers to NULL and lengths to 0  when there
>>    is no remaining space.
>
>Please do this in two patches, one for a single issue fix.

I will change it in next version.

>> 
>> 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 | 34 ++++++++++++++++++++++------------
>>   1 file changed, 22 insertions(+), 12 deletions(-)
>> 
>> diff --git a/drivers/ras/ras.c b/drivers/ras/ras.c
>> index 03df3db62334..e37bf11d0926 100644
>> --- a/drivers/ras/ras.c
>> +++ b/drivers/ras/ras.c
>> @@ -58,10 +58,10 @@ void log_arm_hw_error(struct cper_sec_proc_arm *err, const u8 sev)
>>   	struct cper_arm_err_info *err_info;
>>   	struct cper_arm_ctx_info *ctx_info;
>>   	u8 *ven_err_data;
>> -	u32 ctx_len = 0;
>> +	s32 ctx_len = 0;
>>   	int n, sz, cpu;
>>   	s32 vsei_len;
>> -	u32 pei_len;
>> +	s32 pei_len;
>>   	u8 *pei_err, *ctx_err;
>>   
>>   	pei_len = sizeof(struct cper_arm_err_info) * err->err_info_num;
>> @@ -74,27 +74,37 @@ 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;
>> -
>
>Please leave a empty line here as it is.

I will change it in next version.

>Thanks
>Hanjun
>

             reply	other threads:[~2026-08-25 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 12:21 Liuwenliang (Abbott Liu) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-20 13:18 [PATCH] RAS: Fix out-of-range section_length in ARM processor error handling Abbott Liu
2026-08-22  9:49 ` Hanjun Guo

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=fff991d1207b4548be577ea65e27bc10@huawei.com \
    --to=liuwenliang@huawei.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=douzhaolei@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=jic23@kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.