netdev - arcnet: protocol is buggy messages in 3.0 kernel, not in 2.33 kernel

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-next>] [day] [month] [year] [list]

Message-ID: <CAJDhSdc5J1xzvxYhvru6kjqAbq1NAtvWQCu-tXbi4aE_NXGXrg@mail.gmail.com>
Date:	Thu, 3 May 2012 14:21:11 +0200
From:	Rob Janssen <rob.janssen76@...il.com>
To:	netdev@...r.kernel.org
Subject: arcnet: protocol is buggy messages in 3.0 kernel, not in 2.33 kernel

Hello all

Since we've moved from the 2.33 kernel to the 3.0 kernel, we see the
following kernel messages in dmesg:

protocol 001a is buggy, dev arc0 skb=c702e2f4

The device involved is an arcnet device.
The warning is logged by dev.c, see the following code snippet:

if (skb_network_header(skb2) < skb2->data ||
			    skb2->network_header > skb2->tail) {
				if (net_ratelimit())
					printk(KERN_CRIT "protocol %04x is "
					       "buggy, dev %s skb=%04x\n",
					       ntohs(skb2->protocol),
					       dev->name, skb_network_header(skb2));
				skb_reset_network_header(skb2);
			}
I added some logging, and it appears that skb2->network_header is
placed in memory beyond skb2->tail (the second check).

Does anyone have what causes this message in the 3.0 kernel and/or how
to fix this ?

Thanks in advance,

Rob Janssen
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html