[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YfPCURbOtpGqekyi@kroah.com>
Date: Fri, 28 Jan 2022 11:15:45 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Zhou Qingyang <zhou1615@....edu>
Cc: kjlu@....edu, "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, Lv Zheng <lv.zheng@...el.com>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ACPI: OSL: Fix a NULL pointer dereference in
extlog_init().
On Tue, Jan 25, 2022 at 12:41:34AM +0800, Zhou Qingyang wrote:
> In extlog_init(), acpi_os_map_iomem() is assigned to extlog_l1_hdr and
> there is a dereference of it through l1_head. on the failure of
> acpi_os_map_iomem(), the return value of it could be NULL, which may
> introduce a NULL pointer dereference.
>
> Fix this bug by adding a NULL check of extlog_l1_hdr.
>
> This bug was found by a static analyzer.
>
> Builds with 'make allyesconfig' show no new warnings,
> and our static analyzer no longer warns about this code.
>
> Fixes: a238317ce818 ("ACPI: Clean up acpi_os_map/unmap_memory() to eliminate __iomem.")
> Signed-off-by: Zhou Qingyang <zhou1615@....edu>
> ---
> The analysis employs differential checking to identify inconsistent
> security operations (e.g., checks or kfrees) between two code paths
> and confirms that the inconsistent operations are not recovered in the
> current function or the callers, so they constitute bugs.
>
> Note that, as a bug found by static analysis, it can be a false
> positive or hard to trigger. Multiple researchers have cross-reviewed
> the bug.
Then all of their names need to be on the commit.
Also, as stated before, umn.edu is still not allowed to contribute to
the Linux kernel. Please work with your administration to resolve this
issue.
Powered by blists - more mailing lists