linux-kernel - softmac possible null deref [was: Complete report of Null dereference errors in kernel 2.6.17.1]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 25 Jul 2006 01:01:27 +0100
From:	Daniel Drake <dsd@...too.org>
To:	Tom Walter Dillig <tdillig@...nford.edu>
CC:	linux-kernel@...r.kernel.org, w@....eul,
	kernel_org@...italpeer.com, security@...nel.org,
	Netdev list <netdev@...r.kernel.org>
Subject: softmac possible null deref [was: Complete report of Null dereference
 errors in kernel 2.6.17.1]

Tom Walter Dillig wrote:
> [109]
> 452 net/ieee80211/softmac/ieee80211softmac_io.c
> Possible null dereference of variable "*pkt" in function call
> (include/asm/string.h:__constant_c_and_count_memset) checked at
> (453:net/ieee80211/softmac/ieee80211softmac_io.c)

Either I'm misunderstanding, or this is bogus.

when *pkt is allocated by the various child functions (e.g. 
ieee80211softmac_disassoc_deauth), it is always checked for NULL before 
being used.

Finally, line 453 does another NULL check, so that any failures 
generated above are handled appropriately.

What is the report trying to say?

Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/