[kernel-sec-discuss] r4582 - active

Salvatore Bonaccorso carnil at moszumanska.debian.org
Tue Aug 16 09:19:16 UTC 2016


Author: carnil
Date: 2016-08-16 09:19:16 +0000 (Tue, 16 Aug 2016)
New Revision: 4582

Modified:
   active/CVE-2016-5400
   active/CVE-2016-5412
   active/CVE-2016-5696
   active/CVE-2016-6136
   active/CVE-2016-6156
   active/CVE-2016-6516
Log:
Bump pending version to 4.6.7-1

Modified: active/CVE-2016-5400
===================================================================
--- active/CVE-2016-5400	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-5400	2016-08-16 09:19:16 UTC (rev 4582)
@@ -6,6 +6,6 @@
 upstream: released (4.7) [aa93d1fee85c890a34f2510a310e55ee76a27848]
 3.16-upstream-stable: N/A "Vulnerable code not present"
 3.2-upstream-stable: N/A "Vulnerable code not present"
-sid: pending (4.6.6-1)
+sid: pending (4.6.7-1)
 3.16-jessie-security: N/A "Vulnerable code not present"
 3.2-wheezy-security: N/A "Vulnerable code not present"

Modified: active/CVE-2016-5412
===================================================================
--- active/CVE-2016-5412	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-5412	2016-08-16 09:19:16 UTC (rev 4582)
@@ -9,6 +9,6 @@
 upstream: released (4.8-rc1) [f024ee098476a3e620232e4a78cfac505f121245, 93d17397e4e2182fdaad503e2f9da46202c0f1c3]
 3.16-upstream-stable: pending (3.16.37) [kvm-ppc-book3s-hv-pull-out-tm-state-save-restore-into-separate.patch, kvm-ppc-book3s-hv-save-restore-tm-state-in-h_cede.patch]
 3.2-upstream-stable: N/A "Transactional memory is not supported"
-sid: pending (4.6.6-1) [bugfix/powerpc/kvm-ppc-book3s-hv-pull-out-tm-state-save-restore-int.patch, bugfix/powerpc/kvm-ppc-book3s-hv-save-restore-tm-state-in-h_cede.patch]
+sid: pending (4.6.7-1) [bugfix/powerpc/kvm-ppc-book3s-hv-pull-out-tm-state-save-restore-int.patch, bugfix/powerpc/kvm-ppc-book3s-hv-save-restore-tm-state-in-h_cede.patch]
 3.16-jessie-security: needed
 3.2-wheezy-security: N/A "Transactional memory is not supported"

Modified: active/CVE-2016-5696
===================================================================
--- active/CVE-2016-5696	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-5696	2016-08-16 09:19:16 UTC (rev 4582)
@@ -13,6 +13,6 @@
 upstream: released (4.7) [75ff39ccc1bd5d3c455b6822ab09e533c551f758]
 3.16-upstream-stable: pending (3.16.37) [tcp-make-challenge-acks-less-predictable.patch]
 3.2-upstream-stable: pending (3.2.82) [tcp-make-challenge-acks-less-predictable.patch]
-sid: pending (4.6.6-1) [bugfix/all/tcp-make-challenge-acks-less-predictable.patch]
+sid: pending (4.6.7-1)
 3.16-jessie-security: pending (3.16.36-1+deb8u1) [bugfix/all/tcp-make-challenge-acks-less-predictable.patch]
 3.2-wheezy-security: pending (3.2.81-2) [bugfix/all/tcp-make-challenge-acks-less-predictable.patch]

Modified: active/CVE-2016-6136
===================================================================
--- active/CVE-2016-6136	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-6136	2016-08-16 09:19:16 UTC (rev 4582)
@@ -8,6 +8,6 @@
 upstream: released (4.8-rc1) [43761473c254b45883a64441dd0bc85a42f3645c]
 3.16-upstream-stable: pending (3.16.37) [audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]
 3.2-upstream-stable: pending (3.2.82) [audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]
-sid: pending (4.6.6-1) [bugfix/all/audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]
+sid: pending (4.6.7-1) [bugfix/all/audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]
 3.16-jessie-security: pending (3.16.36-1+deb8u1) [bugfix/all/audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]
 3.2-wheezy-security: pending (3.2.81-2) [bugfix/all/audit-fix-a-double-fetch-in-audit_log_single_execve_arg.patch]

Modified: active/CVE-2016-6156
===================================================================
--- active/CVE-2016-6156	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-6156	2016-08-16 09:19:16 UTC (rev 4582)
@@ -9,6 +9,6 @@
 upstream: released (4.7-rc7) [096cdc6f52225835ff503f987a0d68ef770bb78e]
 3.16-upstream-stable: N/A "Introduced in 4.2-rc1 with a841178445bb72a3d566b4e6ab9d19e9b002eb47"
 3.2-upstream-stable: N/A "Introduced in 4.2-rc1 with a841178445bb72a3d566b4e6ab9d19e9b002eb47"
-sid: pending (4.6.6-1)
+sid: pending (4.6.7-1)
 3.16-jessie-security: N/A "Vulnerable code not present"
 3.2-wheezy-security: N/A "Vulnerable code not present"

Modified: active/CVE-2016-6516
===================================================================
--- active/CVE-2016-6516	2016-08-16 09:15:12 UTC (rev 4581)
+++ active/CVE-2016-6516	2016-08-16 09:19:16 UTC (rev 4582)
@@ -5,6 +5,6 @@
 upstream: released (4.8-rc1) [10eec60ce79187686e052092e5383c99b4420a20]
 3.16-upstream-stable: N/A "Vulnerable code introduced in 4.5-rc1 with 54dbc15172375641ef03399e8f911d7165eb90fb"
 3.2-upstream-stable: N/A "Vulnerable code introduced in 4.5-rc1 with 54dbc15172375641ef03399e8f911d7165eb90fb"
-sid: pending (4.6.6-1)
+sid: pending (4.6.7-1)
 3.16-jessie-security: N/A "Vulnerable code not present"
 3.2-wheezy-security: N/A "Vulnerable code not present"




More information about the kernel-sec-discuss mailing list