-
ASB-2018-05-05_4.142ae46065 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.9-o-mr1bbf4d501 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.9-o-releaseebb5a0ed · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.9-o34ca10e8 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.99731a2da · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4-o-mr1599505a7 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4-o-release6dfbe878 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4-n-release43c5b606 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4-od6e0e386 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4-nc6949a38 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_4.4086f384e · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_3.18-o-mr1969d40b9 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_3.18-o-release3340d256 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_3.18-n-releasee0262eb5 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
ASB-2018-05-05_3.18aaae42a8 · ·
https://source.android.com/security/bulletin/2018-05-01 CVE-2017-16643 CVE-2017-5754 CVE-2018-5344 CVE-2017-15129
-
gpio-v4.17-2e026646c · ·
GPIO fixes for v4.17: - Fix proper IRQ unmasking in the Aspeed driver. - Do not free unrequested descriptors on the errorpath when creating line handles from the userspace chardev requested GPIO lines. - Also fix the errorpath in the linehandle creation function. - Fix the get/set multiple GPIO lines for a few of the funky industrial GPIO cards on the ISA bus.
-
iio-fixes-for-4.17a76974ef9 · ·
First round of IIO fixes for the 4.17 cycle. * core - fix up some issues with overflow etc around wrong types for some fo the kfifo handling functions. Seems unlikely this would be triggered in reality but the fixes are simple so let's tidy them up. Second patch deals with checking the userspace value passed for length for potential overflow. * ad7793 - Catch up with changes to the ad_sigma_delta core and use read_raw / write_raw iwth IIO_CHAN_INFO_SAMP_FEW to handle sampling frequency control. * at91-sama5d2 - Channel config for differential channels was completely broken. - Missing Kconfig dependency for buffer support. * hid-sensor - Fix an issue with powering up after resume due to wrong reference counting. * stm32-dfsdm - Fix an issue with second writes of the oversampling settings failing. - Fix an issue with the sample rate being set to half of requested value when particular clock source is used.
-
-
drm-fixes-for-v4.17-rc4
vmwgfx, i915, vc4, vga dac fixes