From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] Possible null pointer dereference in batman's update_routes
Date: Sat, 27 Sep 2008 18:31:14 +0200 [thread overview]
Message-ID: <200809271831.18672.sven.eckelmann@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
Hi,
I am not sure but I think it could be possible that there is a null pointer
dereference at batman.c:420
I assume that it is possible that neigh_node is NULL and orig_node->router is
also NULL in batman.c:412. Now we dereference neigh_node in batman.c:420 as
third parameter of add_del_route.
I don't know if the third parameter should be set to 0 if neigh_node is NULL
or if the "if"-statement is wrong - so i will not send a patch this time.
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-09-27 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 16:31 Sven Eckelmann [this message]
2008-09-27 17:20 ` [B.A.T.M.A.N.] Possible null pointer dereference in batman's update_routes Marek Lindner
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=200809271831.18672.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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