bionic/linux-raspi2: 4.15.0-1065.69 -proposed tracker

[Marcelo Cerri]

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1885044
packages:
  main: linux-raspi2
  meta: linux-meta-raspi2
phase: Complete
phase-changed: Thursday, 02. July 2020 14:57 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
  bionic/linux-raspi2/pi-kernel: bug 1885037
variant: debs
versions:
  main: 4.15.0-1065.69
  meta: 4.15.0.1065.63

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gavin Lin (gavin.lin)]

Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here:
rpi2-armhf: https://certification.canonical.com/hardware/201906-27188/submission/172945/
rpi3b-arm64: https://certification.canonical.com/hardware/201811-26649/submission/172944/
rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/172954/
rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/172940/
rpi3b+-armhf: https://certification.canonical.com/hardware/201810-26542/submission/172950/
rpi3a+-arm64: https://certification.canonical.com/hardware/201901-26785/submission/172943/
rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/172953/
CM3-arm64: https://certification.canonical.com/hardware/201711-25992/submission/172942/
CM3-armhf: https://certification.canonical.com/hardware/201711-25992/submission/172951/
CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/172939/
CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/172947/

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi2 - 4.15.0-1065.69

---------------
linux-raspi2 (4.15.0-1065.69) bionic; urgency=medium

  * bionic/linux-raspi2: 4.15.0-1065.69 -proposed tracker (LP: #1885038)

  * Build and ship a signed wireguard.ko (LP: #1861284)
    - [Packaging] raspi2: Enable shipping pre-built wireguard

  [ Ubuntu: 4.15.0-109.110 ]

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts
    - update dkms package versions
  * Build and ship a signed wireguard.ko (LP: #1861284)
    - [Packaging] wireguard -- add support for building signed .ko
  * CVE-2019-16089
    - SAUCE: nbd_genl_status: null check for nla_nest_start
  * CVE-2019-19642
    - kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  * CVE-2019-12380
    - efi/x86/Add missing error handling to old_memmap 1:1 mapping code
  * CVE-2019-19039 // CVE-2019-19377
    - btrfs: sink flush_fn to extent_write_cache_pages
    - btrfs: extent_io: Move the BUG_ON() in flush_write_bio() one level up
    - btrfs: Don't submit any btree write bio if the fs has errors
  * CVE-2019-19036
    - btrfs: volumes: Use more straightforward way to calculate map length
    - btrfs: tree-checker: Try to detect missing INODE_ITEM
    - Btrfs: tree-checker: detect file extent items with overlapping ranges
    - Btrfs: make tree checker detect checksum items with overlapping ranges
    - btrfs: harden agaist duplicate fsid on scanned devices
    - Btrfs: fix missing data checksums after replaying a log tree
    - btrfs: reloc: fix reloc root leak and NULL pointer dereference
    - btrfs: Validate child tree block's level and first key
    - btrfs: Detect unbalanced tree with empty leaf before crashing btree
      operations
  * CVE-2019-19318
    - btrfs: tree-checker: Replace root parameter with fs_info
    - btrfs: tree-checker: Check level for leaves and nodes
    - btrfs: tree-checker: get fs_info from eb in generic_err
    - btrfs: tree-checker: get fs_info from eb in file_extent_err
    - btrfs: tree-checker: get fs_info from eb in check_csum_item
    - btrfs: tree-checker: get fs_info from eb in dir_item_err
    - btrfs: tree-checker: get fs_info from eb in check_dir_item
    - btrfs: tree-checker: get fs_info from eb in block_group_err
    - btrfs: tree-checker: get fs_info from eb in check_block_group_item
    - btrfs: tree-checker: get fs_info from eb in check_extent_data_item
    - btrfs: tree-checker: get fs_info from eb in check_leaf_item
    - btrfs: tree-checker: get fs_info from eb in check_leaf
    - btrfs: tree-checker: get fs_info from eb in chunk_err
    - btrfs: tree-checker: get fs_info from eb in dev_item_err
    - btrfs: tree-checker: get fs_info from eb in check_dev_item
    - btrfs: tree-checker: get fs_info from eb in check_inode_item
    - btrfs: tree-checker: Add ROOT_ITEM check
    - btrfs: tree-checker: Add EXTENT_ITEM and METADATA_ITEM check
    - btrfs: tree-checker: Add simple keyed refs check
    - btrfs: tree-checker: Add EXTENT_DATA_REF check
    - btrfs: tree-checker: Fix wrong check on max devid
    - Btrfs: fix selftests failure due to uninitialized i_mode in test inodes
  * CVE-2019-19813 // CVE-2019-19816
    - ...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being set to Fix Released