[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220316074515.jchjdelc722dkug7@pengutronix.de>
Date: Wed, 16 Mar 2022 08:45:15 +0100
From: Marc Kleine-Budde <mkl@...gutronix.de>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Oliver Hartkopp <socketcan@...tkopp.net>, netdev@...r.kernel.org,
syzbot+2339c27f5c66c652843e@...kaller.appspotmail.com
Subject: Re: [net-next] can: isotp: sanitize CAN ID checks in isotp_bind()
On 15.03.2022 18:51:34, Jakub Kicinski wrote:
> On Tue, 15 Mar 2022 21:37:48 +0100 Oliver Hartkopp wrote:
> > Syzbot created an environment that lead to a state machine status that
> > can not be reached with a compliant CAN ID address configuration.
> > The provided address information consisted of CAN ID 0x6000001 and 0xC28001
> > which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.
> >
> > Sanitize the SFF/EFF CAN ID values before performing the address checks.
> >
> > Fixes: e057dd3fc20f ("can: add ISO 15765-2:2016 transport protocol")
> > Reported-by: syzbot+2339c27f5c66c652843e@...kaller.appspotmail.com
> > Signed-off-by: Oliver Hartkopp <socketcan@...tkopp.net>
>
> CC Marc, please make sure you CC maintainers.
Thx. And make sure you have the linux-can ML on Cc :)
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists