From: Jiri Slaby <jirislaby@kernel.org>
To: Zheyu Ma <zheyuma97@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: synclink_gt: Fix null-pointer-dereference in slgt_clean()
Date: Mon, 11 Apr 2022 12:12:59 +0200 [thread overview]
Message-ID: <f9e0d516-d3a7-c0bf-f673-2a4c3dd9184d@kernel.org> (raw)
In-Reply-To: <20220410114814.3920474-1-zheyuma97@gmail.com>
On 10. 04. 22, 13:48, Zheyu Ma wrote:
> When the driver fails at alloc_hdlcdev(), and then we remove the driver
> module, we will get the following splat:
>
> [ 25.065966] general protection fault, probably for non-canonical address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI
> [ 25.066914] KASAN: null-ptr-deref in range [0x0000000000000c10-0x0000000000000c17]
> [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0
> [ 25.077709] Call Trace:
> [ 25.077924] <TASK>
> [ 25.078108] unregister_hdlc_device+0x16/0x30
> [ 25.078481] slgt_cleanup+0x157/0x9f0 [synclink_gt]
>
> Fix this by checking whether the 'info->netdev' is a null pointer first.
Hi,
LGTM
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
Out of curiosity, do you use the driver, or you only do some static
analysis?
> Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
> ---
> drivers/tty/synclink_gt.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/tty/synclink_gt.c b/drivers/tty/synclink_gt.c
> index 25c558e65ece..9bc2a9265277 100644
> --- a/drivers/tty/synclink_gt.c
> +++ b/drivers/tty/synclink_gt.c
> @@ -1746,6 +1746,8 @@ static int hdlcdev_init(struct slgt_info *info)
> */
> static void hdlcdev_exit(struct slgt_info *info)
> {
> + if (!info->netdev)
> + return;
> unregister_hdlc_device(info->netdev);
> free_netdev(info->netdev);
> info->netdev = NULL;
--
js
suse labs
next prev parent reply other threads:[~2022-04-11 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 11:48 Zheyu Ma
2022-04-11 10:12 ` Jiri Slaby [this message]
2022-04-11 10:46 ` Zheyu Ma
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=f9e0d516-d3a7-c0bf-f673-2a4c3dd9184d@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zheyuma97@gmail.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®