Bug 457014 - pppoe: Check packet length on all receive paths [mrg-1]
Summary: pppoe: Check packet length on all receive paths [mrg-1]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 1.1
Hardware: All
OS: Linux
low
low
Target Milestone: 1.0.3
: ---
Assignee: Luis Claudio R. Goncalves
QA Contact:
URL:
Whiteboard:
Depends On: 457013
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-29 08:20 UTC by Eugene Teo (Security Response)
Modified: 2008-10-07 19:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-07 19:21:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0857 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2008-10-07 19:18:59 UTC

Description Eugene Teo (Security Response) 2008-07-29 08:20:45 UTC
+++ This bug was initially created as a clone of Bug #457013 +++

Description of problem:
The length field in the PPPOE header wasn't checked completely. It lacks of a
lower-bound check. Also, call skb_copy_datagram_iovec instead of memcpy_toiovec
so that paged packets (rare for PPPOE) are handled properly.

Comment 2 Luis Claudio R. Goncalves 2008-08-05 18:16:36 UTC
Patch enqueued for -76, applied as is.

Comment 4 David Sommerseth 2008-09-23 08:25:58 UTC
Verified that upstream patch 392fdb0e35055b96faa9c1cd6ab537805337cdce is included in mrt-rt-2.6.24.7-81.

Comment 6 errata-xmlrpc 2008-10-07 19:21:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2008-0857.html


Note You need to log in before you can comment on or make changes to this bug.