Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 271802 (CVE-2009-1633) - Kernel: <2.6.29.4 CIFS unicode DOS (CVE-2009-1633)
Summary: Kernel: <2.6.29.4 CIFS unicode DOS (CVE-2009-1633)
Status: RESOLVED FIXED
Alias: CVE-2009-1633
Product: Gentoo Security
Classification: Unclassified
Component: Kernel (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Security
URL: https://bugzilla.redhat.com/show_bug....
Whiteboard: [linux <2.6.27.24] [linux >=2.6.28 <2...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-29 20:27 UTC by Stefan Behte (RETIRED)
Modified: 2013-09-12 04:55 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Behte (RETIRED) gentoo-dev Security 2009-05-29 20:27:01 UTC
CVE-2009-1633 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2009-1633):
  Multiple buffer overflows in the cifs subsystem in the Linux kernel
  before 2.6.29.4 allow remote CIFS servers to cause a denial of
  service (memory corruption) and possibly have unspecified other
  impact via (1) a malformed Unicode string, related to Unicode string
  area alignment in fs/cifs/sess.c; or (2) long Unicode characters,
  related to fs/cifs/cifssmb.c and the cifs_readdir function in
  fs/cifs/readdir.c.
Comment 1 Kerin Millar 2009-07-24 20:06:44 UTC
I've just spent rather longer than I would have liked figuring out which patches to apply and in which order (with a view to backporting to the next 2.6.28-hardened release). The series is as follows:

27b87fe52baba0a55e9723030e76fce94fabcea4
968460ebd8006d55661dec0fb86712b40d71c413
7b0c8fcff47a885743125dd843db64af41af5a61
d37dc42ab6f040b8f0f2962ab219c5b2accf748d
66345f50f070ae7412a28543ee197cb5eff73598
7fabf0c9479fef9fdb9528a5fbdb1cb744a744a4
69f801fcaa03be83d58c564f00913b7c172808e4
066ce6899484d9026acd6ba3a8dbbedb33d7ae1b
cc20c031bb067eb3280a1c4b5c42295093e24863
59140797c5817363087b0ffb46e6bb81a11fe0dc
460b96960d1946914e50316ffeefe7b41dddce91
f58841666bc22e827ca0dcef7b71c7bc2758ce82
20418acd6874792359b42c12d159f42f17593f34
d185cda7712fd1d9e349174639d76eadc66679be
9e39b0ae8af46c83b85dae7ff5251911a80fce5a
18295796a30cada84e933d805072dc2248d54f98
2edd6c5b0517b9131ede9e74cb121898ccd73042
341060273232a2df0d1a7fa53abc661fcf22747c
afe48c31ea5c74eaac58621ce1c85ae8187c4383
d8e2f53ac99f4ce7d63807a84f98d1b80df598cf

By applying these patches, bug 266638 (CVE-2009-1439) is also closed, and it is *not* necessary (or even possible) to apply the following patches:

5b0ecf297e133be1e4767b1e446a6d7902274c13
a7a7d2fe8813c3bee7d7db9ba889fc2c2dd39dd7