Bug 815266 (CVE-2013-3302) - VUL-0: CVE-2013-3302: kernel: cifs: NULL pointer dereference
Summary: VUL-0: CVE-2013-3302: kernel: cifs: NULL pointer dereference
Status: RESOLVED FIXED
Alias: CVE-2013-3302
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Security Team bot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-15 14:22 UTC by Sebastian Krahmer
Modified: 2013-07-31 17:34 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Krahmer 2013-04-15 14:22:18 UTC 
Via OSS-sec:

Date: Mon, 15 Apr 2013
From: P J P

  Hello,

Linux kernel built with CIFS(CONFIG_CIFS) network file system support is
vulnerable to a NULL pointer dereference flaw. It could occur during a
re-connection attempt.

A user/program could use this flaw to crash the system resulting in a DoS.

Upstream fix:
-------------
 -> https://git.kernel.org/linus/ea702b80e0bbb2448e201472127288beb82ca2fe

Reference:
----------
 -> https://bugzilla.redhat.com/show_bug.cgi?id=952260

Thank you.
--
Prasad J Pandit / Red Hat Security Response Team
DB7A 84C5 D3F9 7CD1 B5EB  C939 D048 7860 3655 602B
Comment 1 Swamp Workflow Management 2013-04-15 22:00:33 UTC 
bugbot adjusting priority
Comment 2 Michal Hocko 2013-04-23 12:13:39 UTC 
marked Cc: <stable@vger.kernel.org> # 3.7+ so I guess the later kernels are not affected. SLE11-SP1-TD checks the sercer->ssocet in smb_sendv.
Comment 3 Sebastian Krahmer 2013-04-29 06:16:36 UTC 
CVE-2013-3302
Comment 4 Marcus Meissner 2013-07-18 09:14:07 UTC 
Suresh, for you?
Comment 5 Jeff Mahoney 2013-07-31 17:34:23 UTC 
What the CC for stable meant is really only 3.7. The fix was upstream in 3.8-rc3 and earlier kernels were unaffected.

We got this fix quite some time ago via 3.7.2.