Home Home > GIT Browse > SLE12-SP3-AZURE
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKernel Build Daemon <kbuild@suse.de>2019-04-19 07:07:18 +0200
committerKernel Build Daemon <kbuild@suse.de>2019-04-19 07:07:18 +0200
commit75e666e3b33d18b5615a7c8343cc3d764e474253 (patch)
treecd7bcd43cccbf0d9c0ae0e3d1cde107d1b178d61
parent7cb8414f2ef8019dbcdc7c0ba4c96bf048100615 (diff)
parentf13f712a828459f50c3466f268d5a7deb80d3851 (diff)
Merge branch 'SLE12-SP3' into SLE12-SP3-AZURESLE12-SP3-AZURE
-rw-r--r--patches.drivers/brcmfmac-Add-length-checks-on-firmware-events.patch2
-rw-r--r--patches.drivers/brcmfmac-add-subtype-check-for-event-handling-in-dat.patch2
2 files changed, 2 insertions, 2 deletions
diff --git a/patches.drivers/brcmfmac-Add-length-checks-on-firmware-events.patch b/patches.drivers/brcmfmac-Add-length-checks-on-firmware-events.patch
index fdf85ec0eb..d49f471d9a 100644
--- a/patches.drivers/brcmfmac-Add-length-checks-on-firmware-events.patch
+++ b/patches.drivers/brcmfmac-Add-length-checks-on-firmware-events.patch
@@ -4,7 +4,7 @@ Date: Wed, 17 Feb 2016 11:26:54 +0100
Subject: [PATCH] brcmfmac: Add length checks on firmware events
Git-commit: 0aedbcaf6f182690790d98d90d5fe1e64c846c34
Patch-mainline: v5.1-rc1
-References: CVE-2019-8564,bsc#1132673
+References: CVE-2019-9503,bsc#1132828
Add additional length checks on firmware events to create more
robust code.
diff --git a/patches.drivers/brcmfmac-add-subtype-check-for-event-handling-in-dat.patch b/patches.drivers/brcmfmac-add-subtype-check-for-event-handling-in-dat.patch
index 1ade7b4366..42161ece2f 100644
--- a/patches.drivers/brcmfmac-add-subtype-check-for-event-handling-in-dat.patch
+++ b/patches.drivers/brcmfmac-add-subtype-check-for-event-handling-in-dat.patch
@@ -4,7 +4,7 @@ Date: Thu, 14 Feb 2019 13:43:48 +0100
Subject: [PATCH] brcmfmac: add subtype check for event handling in data path
Git-commit: a4176ec356c73a46c07c181c6d04039fafa34a9f
Patch-mainline: v5.1-rc1
-References: CVE-2019-8564,bsc#1132673
+References: CVE-2019-9503,bsc#1132828
For USB there is no separate channel being used to pass events
from firmware to the host driver and as such are passed over the