[kernel-sec-discuss] r5036 - active

Ben Hutchings benh at moszumanska.debian.org
Tue Mar 7 00:41:46 UTC 2017


Author: benh
Date: 2017-03-07 00:41:45 +0000 (Tue, 07 Mar 2017)
New Revision: 5036

Modified:
   active/CVE-2017-2596
   active/CVE-2017-5669
   active/CVE-2017-5967
   active/CVE-2017-6347
   active/CVE-2017-6353
Log:
Mark 4.11-rc1 as released

Modified: active/CVE-2017-2596
===================================================================
--- active/CVE-2017-2596	2017-03-05 21:16:07 UTC (rev 5035)
+++ active/CVE-2017-2596	2017-03-07 00:41:45 UTC (rev 5036)
@@ -6,7 +6,7 @@
  bwh> region"
 Bugs:
  https://bugzilla.redhat.com/show_bug.cgi?id=1417812
-upstream: pending (4.11-rc1) [06ce521af9558814b8606c0476c54497cf83a653]
+upstream: released (4.11-rc1) [06ce521af9558814b8606c0476c54497cf83a653]
 4.9-upstream-stable: needed
 3.16-upstream-stable: needed
 3.2-upstream-stable: N/A "Vulnerable code not present"

Modified: active/CVE-2017-5669
===================================================================
--- active/CVE-2017-5669	2017-03-05 21:16:07 UTC (rev 5035)
+++ active/CVE-2017-5669	2017-03-07 00:41:45 UTC (rev 5036)
@@ -5,7 +5,7 @@
  bwh> Confirmed this affects 3.2 with a simple test program
 Bugs:
  https://bugzilla.kernel.org/show_bug.cgi?id=192931
-upstream: pending (4.11-rc1) [95e91b831f87ac8e1f8ed50c14d709089b4e01b8]
+upstream: released (4.11-rc1) [95e91b831f87ac8e1f8ed50c14d709089b4e01b8]
 4.9-upstream-stable: needed
 3.16-upstream-stable: needed
 3.2-upstream-stable: needed

Modified: active/CVE-2017-5967
===================================================================
--- active/CVE-2017-5967	2017-03-05 21:16:07 UTC (rev 5035)
+++ active/CVE-2017-5967	2017-03-07 00:41:45 UTC (rev 5036)
@@ -8,7 +8,7 @@
  bwh> could instead prevent processes outside the initial pid
  bwh> namespace from opening the file.
 Bugs:
-upstream: pending (4.11-rc1) [dfb4357da6ddbdf57d583ba64361c9d792b0e0b1]
+upstream: released (4.11-rc1) [dfb4357da6ddbdf57d583ba64361c9d792b0e0b1]
 4.9-upstream-stable: needed
 3.16-upstream-stable: ignored "Upstream fix is not suitable for backporting"
 3.2-upstream-stable: ignored "Upstream fix is not suitable for backporting"

Modified: active/CVE-2017-6347
===================================================================
--- active/CVE-2017-6347	2017-03-05 21:16:07 UTC (rev 5035)
+++ active/CVE-2017-6347	2017-03-07 00:41:45 UTC (rev 5036)
@@ -4,7 +4,7 @@
  bwh> Introduced in 4.0 by commit ad6f939ab193 "ip: Add offset parameter to
  bwh> ip_cmsg_recv".
 Bugs:
-upstream: pending (4.11-rc1) [ca4ef4574f1ee5252e2cd365f8f5d5bafd048f32]
+upstream: released (4.11-rc1) [ca4ef4574f1ee5252e2cd365f8f5d5bafd048f32]
 4.9-upstream-stable: released (4.9.13) [481aedf869fbf2d4503ca0005dbd68b78422955a]
 3.16-upstream-stable: N/A "Vulnerable code not present"
 3.2-upstream-stable: N/A "Vulnerable code not present"

Modified: active/CVE-2017-6353
===================================================================
--- active/CVE-2017-6353	2017-03-05 21:16:07 UTC (rev 5035)
+++ active/CVE-2017-6353	2017-03-07 00:41:45 UTC (rev 5036)
@@ -8,7 +8,7 @@
  carnil> theless as affected for all branches.
  bwh> Introduced by attempted fix for CVE-2017-5986
 Bugs:
-upstream: pending (4.11-rc1) [dfcb9f4f99f1e9a49e43398a7bfbf56927544af1]
+upstream: released (4.11-rc1) [dfcb9f4f99f1e9a49e43398a7bfbf56927544af1]
 4.9-upstream-stable: needed
 3.16-upstream-stable: needed
 3.2-upstream-stable: needed




More information about the kernel-sec-discuss mailing list