netdev - Re: [PATCH net-next] dp83640: Fix length check for event timestamp status messages

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

Date:	Fri, 22 Aug 2014 12:36:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	christian.riesch@...cron.at
Cc:	netdev@...r.kernel.org, richardcochran@...il.com
Subject: Re: [PATCH net-next] dp83640: Fix length check for event timestamp
 status messages

From: Christian Riesch <christian.riesch@...cron.at>
Date: Thu, 21 Aug 2014 15:17:04 +0200

> Event timestamp status messages have a variable length, ranging from
> 1 to 5 words (16 bit words). The current code however requires
> a minimum message length of sizeof(*phy_txts). In most cases this
> condition is fulfilled due to padding bytes. However, if several events
> are signaled in a single message, padding bytes may not be present.
> For short event timestamp status messages, the length check will fail,
> and the event timestamp will be dropped.
> 
> Signed-off-by: Christian Riesch <christian.riesch@...cron.at>

Applied.
--
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