Free software activities in May, June and July 2019
Hi Planet, it is been a long time since my last post.
Here is an update covering what I have been doing in my free software activities during May, June and July 2019.
As a first contribution, Kees Cook asked me to check all the NLA_STRING for non-nul terminated strings. Internal functions of NLA attrs expect to have standard nul-terminated strings and use standard strings functions like strcmp() or equivalent. Few drivers were using non-nul terminated strings in some cases, which might lead to buffer overflow. I have checked all the NLA_STRING uses in all drivers and forwarded a status for all of these. Everything were already fixed in linux-next (hopefully).
Here is an update covering what I have been doing in my free software activities during May, June and July 2019.
May
Only contributions related to Debian were done in May- linux: Update to 5.1 (including porting of all debian patches to the new release)
- linux: Update to 5.1.2
- linux: Update to 5.1.3
- linux: Update to 5.1.5
- firmware-nonfree: misc-nonfree: Add GV100 signed firmwares (Closes: #928672)
June
Debian
- linux: Update to 5.1.7
- linux: Update to 5.1.8
- linux: Update to 5.1.10
- linux: Update to 5.1.11
- linux: Update to 5.1.15
- linux: [sparc64] Fix device naming inconsistency between sunhv_console and sunhv_reg (Closes: #926539)
- raspi3-firmware: New upstream version 1.20190517
- raspi3-firmware: New upstream version 1.20190620+1
Kernel Self Protection Project
I have recently joined the kernel self protection protect, which basically intends to harden the mainline linux kernel the most as possible by adding subsystems that improve the security or make internal subsystems more robust to some common errors that might lead to security issues.As a first contribution, Kees Cook asked me to check all the NLA_STRING for non-nul terminated strings. Internal functions of NLA attrs expect to have standard nul-terminated strings and use standard strings functions like strcmp() or equivalent. Few drivers were using non-nul terminated strings in some cases, which might lead to buffer overflow. I have checked all the NLA_STRING uses in all drivers and forwarded a status for all of these. Everything were already fixed in linux-next (hopefully).
July
Debian
- linux: Update to 5.1.16
- linux: Update to 5.2-rc7 (including porting of all debian patches to the new release)
- linux: Update to 5.2
- linux: Update to 5.2.1
- linux: [rt] Update to 5.2-rt1
- linux: Update to 5.2.4
- ethtool: New upstream version 5.2
- raspi3-firmware: Fixed lintians warnings about the binaries blobs for the raspberry PI 4
- raspi3-firmware: New upstream version 1.20190709
- raspi3-firmware: New upstream version 1.20190718
- linux: [x86] x86/insn-eval: Fix use-after-free access to LDT entry (CVE-2019-13233)
- linux: [powerpc*] mm/64s/hash: Reallocate context ids on fork (CVE-2019-12817)
- linux: nfc: Ensure presence of required attributes in the deactivate_target handler (CVE-2019-12984)
- linux: binder: fix race between munmap() and direct reclaim (CVE-2019-1999)
- linux: scsi: libsas: fix a race condition when smp task timeout (CVE-2018-20836)
- linux: Input: gtco - bounds check collection indent level (CVE-2019-13631)
Commentaires
Enregistrer un commentaire