summaryrefslogtreecommitdiffstats
path: root/retired/CVE-2018-9415
diff options
context:
space:
mode:
authorSalvatore Bonaccorso <carnil@debian.org>2018-07-10 06:19:37 +0200
committerSalvatore Bonaccorso <carnil@debian.org>2018-07-10 06:19:37 +0200
commit37b052bbca367b8dbe899620378a87dea1dab6e6 (patch)
treedf156d47b2669d93ff07fd1e7ece0ab1ef5841a7 /retired/CVE-2018-9415
parent2c65429f6eae1f43d3071058912feaac103e7fd0 (diff)
Add upstream commit for CVE-2018-9415
Unretire only for tracking purpose until the point release for 9.5 happened.
Diffstat (limited to 'retired/CVE-2018-9415')
-rw-r--r--retired/CVE-2018-941519
1 files changed, 0 insertions, 19 deletions
diff --git a/retired/CVE-2018-9415 b/retired/CVE-2018-9415
deleted file mode 100644
index 436131cc..00000000
--- a/retired/CVE-2018-9415
+++ /dev/null
@@ -1,19 +0,0 @@
-Description:
-References:
- https://source.android.com/security/bulletin/pixel/2018-07-01
- https://patchwork.kernel.org/patch/9946759/
-Notes:
- jmm> Unclear, might affect drivers/amba in some way?
- bwh> The Android bulletin links to a patch for PCI that *wasn't*
- bwh> applied upstream (and isn't needed), but based on the
- bwh> description as "AMBA driver" I found what I think is the actual
- bwh> upstream fix.
- bwh> Introduced in Linux 4.0 by commit 3cf385713460 "ARM: 8256/1:
- bwh> driver coamba: add device binding path 'driver_override'".
-Bugs:
-upstream: released (4.17-rc3) [d2ffed5185df9d8d9ccd150e4340e3b6f96a8381]
-4.9-upstream-stable: released (4.9.98)
-3.16-upstream-stable: N/A "Vulnerable code not present"
-sid: released (4.16.12-1)
-4.9-stretch-security: pending (4.9.107-1)
-3.16-jessie-security: N/A "Vulnerable code not present"

© 2014-2024 Faster IT GmbH | imprint | privacy policy