linux-kernel - Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb

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:	Sun, 22 Feb 2009 13:47:18 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Sitsofe Wheeler <sitsofe@...oo.com>
CC:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
	ath5k-devel@...ema.h4ckr.net,
	Nick Kossifidis <mickflemm@...il.com>,
	"Luis R. Rodriguez" <lrodriguez@...eros.com>, Bob Copeland <me@bob>
Subject: Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)

On 22.2.2009 13:20, Sitsofe Wheeler wrote:
> On Sun, Feb 22, 2009 at 01:01:21PM +0100, Jiri Slaby wrote:
>> The unsupported jumbo message might be a clue. When we jump to the next:
>> label, the buffer is at the end of the list in software, while in
>> hardware it isn't. In theory, we might hit the bug with rx buffers
>> exhaustion, because the test (bf_last == bf) doesn't work as expected then.
>
> This seems to be happening somewhat regularly now - I've got a small
> collections of the warnings (I'll include them below in case they are
> any help):
[...]
> [11207.741042]   Object 0xd7060000:  6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
> [11207.741071]   Object 0xd7060010:  80 00 00 00 ff ff ff ff ff ff 00 30 ab 1a 32 3f ....ÿÿÿÿÿÿ.0«.2?

All of them are almost the same scenario, the last one was data not 
beacon, but it's irrelevant. And previously I was wrong, we move the 
buffer to the end even on hardware side. Thanks so far, I personally see 
no reason for this to happen yet.
--
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/