Bug 698190 - VUL-1: kernel: does not properly manage a backlog of received packets,
VUL-1: kernel: does not properly manage a backlog of received packets,
Status: RESOLVED FIXED
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: General
unspecified
Other Other
: P5 - None : Critical
: ---
Assigned To: E-mail List
Security Team bot
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-06 09:25 UTC by Thomas Biege
Modified: 2011-06-08 13:45 UTC (History)
4 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Biege 2011-06-06 09:25:12 UTC
Hi.
There is a security bug in package 'kernel'.

This bug is public.

There is no coordinated release date (CRD) set.

CVE number: CVE-2010-4805
CVE description: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4805
CVSS v2 Base Score: 6.1 (moderate) (AV:A/AC:L/Au:N/C:N/I:N/A:C)
Resource Management Errors (CWE-399)


Original posting:


 remote denial of service
CVE-ID: CVE-2010-4805
URL: 

The socket implementation in net/core/sock.c in the Linux kernel before 2.6.35 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service by sending a large amount of network traffic, related to the sk_add_backlog function and the sk_rmem_alloc socket field.  NOTE: this vulnerability exists because of an incomplete fix for CVE-YYYY-NNN.
    
    
Reference: CONFIRM: https://bugzilla.redhat.com/show_bug.cgi?id=657303
Reference: MLIST: http://kerneltrap.org/mailarchive/linux-netdev/2010/3/3/6271093/thread
Reference: CONFIRM: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c377411f2494a931ff7facdbb3a6839b1266bcf6
Reference: BID: http://www.securityfocus.com/bid/46637
Reference: CONFIRM: http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.35
Comment 1 Jiri Bohac 2011-06-07 10:05:32 UTC
Could this be a duplicate of Bug #655973? The upstream commit c377411f2494a931ff7facdbb3a6839b1266bcf6 got applied to our kernel trees already in the patch series from that bug.
Comment 2 Marcus Meissner 2011-06-08 13:45:27 UTC
yes, we got it already.

i checked sle11 sp1, it has the patch, same for sle10 sp3 and sp4.

so yes, it is fixed already.

thanks!