linux - Debian Package Tracker

general

source: linux (main)
version: 5.15.15-1
maintainer: Debian Kernel Team (archive) (DMD)
uploaders: maximilian attems [DMD] – Salvatore Bonaccorso [DMD] – Ben Hutchings [DMD] – Bastian Blank [DMD]
arch: all
std-ver: 4.2.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 4.9.228-1
o-o-sec: 4.9.290-1
o-o-bpo: 4.19.118-2+deb10u1~bpo9+1
oldstable: 4.19.208-1
old-sec: 4.19.194-3
old-bpo: 5.10.70-1~bpo10+1
stable: 5.10.84-1
stable-sec: 5.10.92-1
stable-bpo: 5.15.5-2~bpo11+1
testing: 5.15.15-1
unstable: 5.15.15-1
exp: 5.16~rc8-1~exp1

versioned links

4.9.228-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.9.246-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.9.258-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.9.272-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.9.290-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.19.118-2+deb10u1~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.19.171-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.19.194-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.19.208-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.10.46-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.10.70-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.10.70-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.10.84-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.10.92-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.14.9-2~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.15.5-2~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.15.15-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.16~rc7-1~exp1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.16~rc8-1~exp1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

acpi-modules-5.15.0-3-686-di
acpi-modules-5.15.0-3-686-pae-di
acpi-modules-5.15.0-3-amd64-di
affs-modules-5.15.0-3-4kc-malta-di
affs-modules-5.15.0-3-5kc-malta-di
affs-modules-5.15.0-3-loongson-3-di
affs-modules-5.15.0-3-m68k-di
affs-modules-5.15.0-3-octeon-di
affs-modules-5.15.0-3-powerpc-di
affs-modules-5.15.0-3-powerpc64-di
ata-modules-5.15.0-3-4kc-malta-di
ata-modules-5.15.0-3-5kc-malta-di
ata-modules-5.15.0-3-686-di
ata-modules-5.15.0-3-686-pae-di
ata-modules-5.15.0-3-alpha-generic-di
ata-modules-5.15.0-3-amd64-di
ata-modules-5.15.0-3-arm64-di
ata-modules-5.15.0-3-armmp-di
ata-modules-5.15.0-3-itanium-di
ata-modules-5.15.0-3-loongson-3-di
ata-modules-5.15.0-3-m68k-di
ata-modules-5.15.0-3-parisc-di
ata-modules-5.15.0-3-parisc64-di
ata-modules-5.15.0-3-powerpc-di
ata-modules-5.15.0-3-powerpc64-di
ata-modules-5.15.0-3-powerpc64le-di
ata-modules-5.15.0-3-riscv64-di
ata-modules-5.15.0-3-sparc64-di
bpftool (2 bugs: 0, 0, 2, 0)
btrfs-modules-5.15.0-3-4kc-malta-di
btrfs-modules-5.15.0-3-5kc-malta-di
btrfs-modules-5.15.0-3-686-di
btrfs-modules-5.15.0-3-686-pae-di
btrfs-modules-5.15.0-3-alpha-generic-di
btrfs-modules-5.15.0-3-amd64-di
btrfs-modules-5.15.0-3-arm64-di
btrfs-modules-5.15.0-3-armmp-di
btrfs-modules-5.15.0-3-itanium-di
btrfs-modules-5.15.0-3-loongson-3-di
btrfs-modules-5.15.0-3-m68k-di
btrfs-modules-5.15.0-3-marvell-di
btrfs-modules-5.15.0-3-mips32r6-di
btrfs-modules-5.15.0-3-mips32r6el-di
btrfs-modules-5.15.0-3-mips64r6-di
btrfs-modules-5.15.0-3-mips64r6el-di
btrfs-modules-5.15.0-3-octeon-di
btrfs-modules-5.15.0-3-parisc-di
btrfs-modules-5.15.0-3-parisc64-di
btrfs-modules-5.15.0-3-powerpc-di
btrfs-modules-5.15.0-3-powerpc64-di
btrfs-modules-5.15.0-3-powerpc64le-di
btrfs-modules-5.15.0-3-riscv64-di
btrfs-modules-5.15.0-3-s390x-di
btrfs-modules-5.15.0-3-sh7751r-di
btrfs-modules-5.15.0-3-sh7785lcr-di
btrfs-modules-5.15.0-3-sparc64-di
cdrom-core-modules-5.15.0-3-4kc-malta-di
cdrom-core-modules-5.15.0-3-5kc-malta-di
cdrom-core-modules-5.15.0-3-686-di
cdrom-core-modules-5.15.0-3-686-pae-di
cdrom-core-modules-5.15.0-3-alpha-generic-di
cdrom-core-modules-5.15.0-3-amd64-di
cdrom-core-modules-5.15.0-3-arm64-di
cdrom-core-modules-5.15.0-3-armmp-di
cdrom-core-modules-5.15.0-3-itanium-di
cdrom-core-modules-5.15.0-3-loongson-3-di
cdrom-core-modules-5.15.0-3-m68k-di
cdrom-core-modules-5.15.0-3-marvell-di
cdrom-core-modules-5.15.0-3-octeon-di
cdrom-core-modules-5.15.0-3-parisc-di
cdrom-core-modules-5.15.0-3-parisc64-di
cdrom-core-modules-5.15.0-3-powerpc-di
cdrom-core-modules-5.15.0-3-powerpc64-di
cdrom-core-modules-5.15.0-3-powerpc64le-di
cdrom-core-modules-5.15.0-3-riscv64-di
cdrom-core-modules-5.15.0-3-s390x-di
cdrom-core-modules-5.15.0-3-sh7751r-di
cdrom-core-modules-5.15.0-3-sh7785lcr-di
cdrom-core-modules-5.15.0-3-sparc64-di
crc-modules-5.15.0-3-4kc-malta-di
crc-modules-5.15.0-3-5kc-malta-di
crc-modules-5.15.0-3-686-di
crc-modules-5.15.0-3-686-pae-di
crc-modules-5.15.0-3-alpha-generic-di
crc-modules-5.15.0-3-amd64-di
crc-modules-5.15.0-3-arm64-di
crc-modules-5.15.0-3-armmp-di
crc-modules-5.15.0-3-itanium-di
crc-modules-5.15.0-3-loongson-3-di
crc-modules-5.15.0-3-m68k-di
crc-modules-5.15.0-3-marvell-di
crc-modules-5.15.0-3-mips32r6-di
crc-modules-5.15.0-3-mips32r6el-di
crc-modules-5.15.0-3-mips64r6-di
crc-modules-5.15.0-3-mips64r6el-di
crc-modules-5.15.0-3-octeon-di
crc-modules-5.15.0-3-parisc-di
crc-modules-5.15.0-3-parisc64-di
crc-modules-5.15.0-3-powerpc-di
crc-modules-5.15.0-3-powerpc64-di
crc-modules-5.15.0-3-powerpc64le-di
crc-modules-5.15.0-3-riscv64-di
crc-modules-5.15.0-3-s390x-di
crc-modules-5.15.0-3-sh7751r-di
crc-modules-5.15.0-3-sh7785lcr-di
crc-modules-5.15.0-3-sparc64-di
crypto-dm-modules-5.15.0-3-4kc-malta-di
crypto-dm-modules-5.15.0-3-5kc-malta-di
crypto-dm-modules-5.15.0-3-686-di
crypto-dm-modules-5.15.0-3-686-pae-di
crypto-dm-modules-5.15.0-3-alpha-generic-di
crypto-dm-modules-5.15.0-3-amd64-di
crypto-dm-modules-5.15.0-3-arm64-di
crypto-dm-modules-5.15.0-3-armmp-di
crypto-dm-modules-5.15.0-3-itanium-di
crypto-dm-modules-5.15.0-3-loongson-3-di
crypto-dm-modules-5.15.0-3-marvell-di
crypto-dm-modules-5.15.0-3-mips32r6-di
crypto-dm-modules-5.15.0-3-mips32r6el-di
crypto-dm-modules-5.15.0-3-mips64r6-di
crypto-dm-modules-5.15.0-3-mips64r6el-di
crypto-dm-modules-5.15.0-3-octeon-di
crypto-dm-modules-5.15.0-3-parisc-di
crypto-dm-modules-5.15.0-3-parisc64-di
crypto-dm-modules-5.15.0-3-powerpc-di
crypto-dm-modules-5.15.0-3-powerpc64-di
crypto-dm-modules-5.15.0-3-powerpc64le-di
crypto-dm-modules-5.15.0-3-riscv64-di
crypto-dm-modules-5.15.0-3-s390x-di
crypto-dm-modules-5.15.0-3-sh7751r-di
crypto-dm-modules-5.15.0-3-sh7785lcr-di
crypto-dm-modules-5.15.0-3-sparc64-di
crypto-modules-5.15.0-3-4kc-malta-di
crypto-modules-5.15.0-3-5kc-malta-di
crypto-modules-5.15.0-3-686-di
crypto-modules-5.15.0-3-686-pae-di
crypto-modules-5.15.0-3-alpha-generic-di
crypto-modules-5.15.0-3-amd64-di
crypto-modules-5.15.0-3-arm64-di
crypto-modules-5.15.0-3-armmp-di
crypto-modules-5.15.0-3-itanium-di
crypto-modules-5.15.0-3-loongson-3-di
crypto-modules-5.15.0-3-m68k-di
crypto-modules-5.15.0-3-marvell-di
crypto-modules-5.15.0-3-mips32r6-di
crypto-modules-5.15.0-3-mips32r6el-di
crypto-modules-5.15.0-3-mips64r6-di
crypto-modules-5.15.0-3-mips64r6el-di
crypto-modules-5.15.0-3-octeon-di
crypto-modules-5.15.0-3-parisc-di
crypto-modules-5.15.0-3-parisc64-di
crypto-modules-5.15.0-3-powerpc-di
crypto-modules-5.15.0-3-powerpc64-di
crypto-modules-5.15.0-3-powerpc64le-di
crypto-modules-5.15.0-3-riscv64-di
crypto-modules-5.15.0-3-s390x-di
crypto-modules-5.15.0-3-sh7751r-di
crypto-modules-5.15.0-3-sh7785lcr-di
crypto-modules-5.15.0-3-sparc64-di
dasd-extra-modules-5.15.0-3-s390x-di
dasd-modules-5.15.0-3-s390x-di
efi-modules-5.15.0-3-686-di
efi-modules-5.15.0-3-686-pae-di
efi-modules-5.15.0-3-amd64-di
efi-modules-5.15.0-3-arm64-di
efi-modules-5.15.0-3-armmp-di
event-modules-5.15.0-3-4kc-malta-di
event-modules-5.15.0-3-5kc-malta-di
event-modules-5.15.0-3-686-di
event-modules-5.15.0-3-686-pae-di
event-modules-5.15.0-3-alpha-generic-di
event-modules-5.15.0-3-amd64-di
event-modules-5.15.0-3-arm64-di
event-modules-5.15.0-3-armmp-di
event-modules-5.15.0-3-itanium-di
event-modules-5.15.0-3-loongson-3-di
event-modules-5.15.0-3-marvell-di
event-modules-5.15.0-3-octeon-di
event-modules-5.15.0-3-parisc-di
event-modules-5.15.0-3-parisc64-di
event-modules-5.15.0-3-powerpc-di
event-modules-5.15.0-3-powerpc64-di
event-modules-5.15.0-3-powerpc64le-di
event-modules-5.15.0-3-riscv64-di
ext4-modules-5.15.0-3-4kc-malta-di
ext4-modules-5.15.0-3-5kc-malta-di
ext4-modules-5.15.0-3-686-di
ext4-modules-5.15.0-3-686-pae-di
ext4-modules-5.15.0-3-alpha-generic-di
ext4-modules-5.15.0-3-amd64-di
ext4-modules-5.15.0-3-arm64-di
ext4-modules-5.15.0-3-armmp-di
ext4-modules-5.15.0-3-itanium-di
ext4-modules-5.15.0-3-loongson-3-di
ext4-modules-5.15.0-3-m68k-di
ext4-modules-5.15.0-3-marvell-di
ext4-modules-5.15.0-3-mips32r6-di
ext4-modules-5.15.0-3-mips32r6el-di
ext4-modules-5.15.0-3-mips64r6-di
ext4-modules-5.15.0-3-mips64r6el-di
ext4-modules-5.15.0-3-octeon-di
ext4-modules-5.15.0-3-parisc-di
ext4-modules-5.15.0-3-parisc64-di
ext4-modules-5.15.0-3-powerpc-di
ext4-modules-5.15.0-3-powerpc64-di
ext4-modules-5.15.0-3-powerpc64le-di
ext4-modules-5.15.0-3-riscv64-di
ext4-modules-5.15.0-3-s390x-di
ext4-modules-5.15.0-3-sh7751r-di
ext4-modules-5.15.0-3-sh7785lcr-di
ext4-modules-5.15.0-3-sparc64-di
f2fs-modules-5.15.0-3-4kc-malta-di
f2fs-modules-5.15.0-3-5kc-malta-di
f2fs-modules-5.15.0-3-686-di
f2fs-modules-5.15.0-3-686-pae-di
f2fs-modules-5.15.0-3-alpha-generic-di
f2fs-modules-5.15.0-3-amd64-di
f2fs-modules-5.15.0-3-arm64-di
f2fs-modules-5.15.0-3-armmp-di
f2fs-modules-5.15.0-3-itanium-di
f2fs-modules-5.15.0-3-loongson-3-di
f2fs-modules-5.15.0-3-marvell-di
f2fs-modules-5.15.0-3-mips32r6-di
f2fs-modules-5.15.0-3-mips32r6el-di
f2fs-modules-5.15.0-3-mips64r6-di
f2fs-modules-5.15.0-3-mips64r6el-di
f2fs-modules-5.15.0-3-octeon-di
f2fs-modules-5.15.0-3-parisc-di
f2fs-modules-5.15.0-3-parisc64-di
f2fs-modules-5.15.0-3-powerpc-di
f2fs-modules-5.15.0-3-powerpc64-di
f2fs-modules-5.15.0-3-powerpc64le-di
f2fs-modules-5.15.0-3-riscv64-di
f2fs-modules-5.15.0-3-s390x-di
f2fs-modules-5.15.0-3-sh7751r-di
f2fs-modules-5.15.0-3-sh7785lcr-di
f2fs-modules-5.15.0-3-sparc64-di
fancontrol-modules-5.15.0-3-powerpc64-di
fancontrol-modules-5.15.0-3-powerpc64le-di
fat-modules-5.15.0-3-4kc-malta-di
fat-modules-5.15.0-3-5kc-malta-di
fat-modules-5.15.0-3-686-di
fat-modules-5.15.0-3-686-pae-di
fat-modules-5.15.0-3-alpha-generic-di
fat-modules-5.15.0-3-amd64-di
fat-modules-5.15.0-3-arm64-di
fat-modules-5.15.0-3-armmp-di
fat-modules-5.15.0-3-itanium-di
fat-modules-5.15.0-3-loongson-3-di
fat-modules-5.15.0-3-m68k-di
fat-modules-5.15.0-3-marvell-di
fat-modules-5.15.0-3-octeon-di
fat-modules-5.15.0-3-parisc-di
fat-modules-5.15.0-3-parisc64-di
fat-modules-5.15.0-3-powerpc-di
fat-modules-5.15.0-3-powerpc64-di
fat-modules-5.15.0-3-powerpc64le-di
fat-modules-5.15.0-3-riscv64-di
fat-modules-5.15.0-3-s390x-di
fat-modules-5.15.0-3-sh7751r-di
fat-modules-5.15.0-3-sh7785lcr-di
fat-modules-5.15.0-3-sparc64-di
fb-modules-5.15.0-3-4kc-malta-di
fb-modules-5.15.0-3-5kc-malta-di
fb-modules-5.15.0-3-686-di
fb-modules-5.15.0-3-686-pae-di
fb-modules-5.15.0-3-alpha-generic-di
fb-modules-5.15.0-3-amd64-di
fb-modules-5.15.0-3-arm64-di
fb-modules-5.15.0-3-armmp-di
fb-modules-5.15.0-3-itanium-di
fb-modules-5.15.0-3-loongson-3-di
fb-modules-5.15.0-3-marvell-di
fb-modules-5.15.0-3-parisc64-di
fb-modules-5.15.0-3-powerpc-di
fb-modules-5.15.0-3-powerpc64-di
fb-modules-5.15.0-3-powerpc64le-di
fb-modules-5.15.0-3-riscv64-di
fb-modules-5.15.0-3-sparc64-di
firewire-core-modules-5.15.0-3-686-di
firewire-core-modules-5.15.0-3-686-pae-di
firewire-core-modules-5.15.0-3-amd64-di
firewire-core-modules-5.15.0-3-itanium-di
firewire-core-modules-5.15.0-3-loongson-3-di
firewire-core-modules-5.15.0-3-powerpc-di
firewire-core-modules-5.15.0-3-powerpc64-di
firewire-core-modules-5.15.0-3-powerpc64le-di
firewire-core-modules-5.15.0-3-sh7751r-di
firewire-core-modules-5.15.0-3-sh7785lcr-di
fuse-modules-5.15.0-3-4kc-malta-di
fuse-modules-5.15.0-3-5kc-malta-di
fuse-modules-5.15.0-3-686-di
fuse-modules-5.15.0-3-686-pae-di
fuse-modules-5.15.0-3-alpha-generic-di
fuse-modules-5.15.0-3-amd64-di
fuse-modules-5.15.0-3-arm64-di
fuse-modules-5.15.0-3-armmp-di
fuse-modules-5.15.0-3-itanium-di
fuse-modules-5.15.0-3-loongson-3-di
fuse-modules-5.15.0-3-m68k-di
fuse-modules-5.15.0-3-marvell-di
fuse-modules-5.15.0-3-mips32r6-di
fuse-modules-5.15.0-3-mips32r6el-di
fuse-modules-5.15.0-3-mips64r6-di
fuse-modules-5.15.0-3-mips64r6el-di
fuse-modules-5.15.0-3-octeon-di
fuse-modules-5.15.0-3-parisc-di
fuse-modules-5.15.0-3-parisc64-di
fuse-modules-5.15.0-3-powerpc-di
fuse-modules-5.15.0-3-powerpc64-di
fuse-modules-5.15.0-3-powerpc64le-di
fuse-modules-5.15.0-3-riscv64-di
fuse-modules-5.15.0-3-s390x-di
fuse-modules-5.15.0-3-sh7751r-di
fuse-modules-5.15.0-3-sh7785lcr-di
fuse-modules-5.15.0-3-sparc64-di
hfs-modules-5.15.0-3-m68k-di
hfs-modules-5.15.0-3-powerpc-di
hfs-modules-5.15.0-3-powerpc64-di
hyperv-daemons (1 bugs: 0, 1, 0, 0)
hypervisor-modules-5.15.0-3-powerpc64-di
hypervisor-modules-5.15.0-3-powerpc64le-di
i2c-modules-5.15.0-3-4kc-malta-di
i2c-modules-5.15.0-3-5kc-malta-di
i2c-modules-5.15.0-3-686-di
i2c-modules-5.15.0-3-686-pae-di
i2c-modules-5.15.0-3-alpha-generic-di
i2c-modules-5.15.0-3-amd64-di
i2c-modules-5.15.0-3-arm64-di
i2c-modules-5.15.0-3-armmp-di
i2c-modules-5.15.0-3-itanium-di
i2c-modules-5.15.0-3-powerpc64-di
i2c-modules-5.15.0-3-powerpc64le-di
i2c-modules-5.15.0-3-riscv64-di
i2c-modules-5.15.0-3-sh7751r-di
i2c-modules-5.15.0-3-sparc64-di
input-modules-5.15.0-3-4kc-malta-di
input-modules-5.15.0-3-5kc-malta-di
input-modules-5.15.0-3-686-di
input-modules-5.15.0-3-686-pae-di
input-modules-5.15.0-3-alpha-generic-di
input-modules-5.15.0-3-amd64-di
input-modules-5.15.0-3-arm64-di
input-modules-5.15.0-3-armmp-di
input-modules-5.15.0-3-itanium-di
input-modules-5.15.0-3-loongson-3-di
input-modules-5.15.0-3-marvell-di
input-modules-5.15.0-3-octeon-di
input-modules-5.15.0-3-parisc-di
input-modules-5.15.0-3-parisc64-di
input-modules-5.15.0-3-powerpc-di
input-modules-5.15.0-3-powerpc64-di
input-modules-5.15.0-3-powerpc64le-di
input-modules-5.15.0-3-riscv64-di
input-modules-5.15.0-3-sparc64-di
ipv6-modules-5.15.0-3-marvell-di
isofs-modules-5.15.0-3-4kc-malta-di
isofs-modules-5.15.0-3-5kc-malta-di
isofs-modules-5.15.0-3-686-di
isofs-modules-5.15.0-3-686-pae-di
isofs-modules-5.15.0-3-alpha-generic-di
isofs-modules-5.15.0-3-amd64-di
isofs-modules-5.15.0-3-arm64-di
isofs-modules-5.15.0-3-armmp-di
isofs-modules-5.15.0-3-itanium-di
isofs-modules-5.15.0-3-loongson-3-di
isofs-modules-5.15.0-3-m68k-di
isofs-modules-5.15.0-3-marvell-di
isofs-modules-5.15.0-3-mips32r6-di
isofs-modules-5.15.0-3-mips32r6el-di
isofs-modules-5.15.0-3-mips64r6-di
isofs-modules-5.15.0-3-mips64r6el-di
isofs-modules-5.15.0-3-octeon-di
isofs-modules-5.15.0-3-parisc-di
isofs-modules-5.15.0-3-parisc64-di
isofs-modules-5.15.0-3-powerpc-di
isofs-modules-5.15.0-3-powerpc64-di
isofs-modules-5.15.0-3-powerpc64le-di
isofs-modules-5.15.0-3-riscv64-di
isofs-modules-5.15.0-3-s390x-di
isofs-modules-5.15.0-3-sh7751r-di
isofs-modules-5.15.0-3-sh7785lcr-di
isofs-modules-5.15.0-3-sparc64-di
jffs2-modules-5.15.0-3-marvell-di
jfs-modules-5.15.0-3-4kc-malta-di
jfs-modules-5.15.0-3-5kc-malta-di
jfs-modules-5.15.0-3-686-di
jfs-modules-5.15.0-3-686-pae-di
jfs-modules-5.15.0-3-alpha-generic-di
jfs-modules-5.15.0-3-amd64-di
jfs-modules-5.15.0-3-arm64-di
jfs-modules-5.15.0-3-armmp-di
jfs-modules-5.15.0-3-itanium-di
jfs-modules-5.15.0-3-loongson-3-di
jfs-modules-5.15.0-3-marvell-di
jfs-modules-5.15.0-3-mips32r6-di
jfs-modules-5.15.0-3-mips32r6el-di
jfs-modules-5.15.0-3-mips64r6-di
jfs-modules-5.15.0-3-mips64r6el-di
jfs-modules-5.15.0-3-octeon-di
jfs-modules-5.15.0-3-parisc-di
jfs-modules-5.15.0-3-parisc64-di
jfs-modules-5.15.0-3-powerpc-di
jfs-modules-5.15.0-3-powerpc64-di
jfs-modules-5.15.0-3-powerpc64le-di
jfs-modules-5.15.0-3-riscv64-di
jfs-modules-5.15.0-3-sh7751r-di
jfs-modules-5.15.0-3-sh7785lcr-di
jfs-modules-5.15.0-3-sparc64-di
kernel-image-5.15.0-3-4kc-malta-di
kernel-image-5.15.0-3-5kc-malta-di
kernel-image-5.15.0-3-686-di
kernel-image-5.15.0-3-686-pae-di
kernel-image-5.15.0-3-alpha-generic-di
kernel-image-5.15.0-3-amd64-di
kernel-image-5.15.0-3-arm64-di
kernel-image-5.15.0-3-armmp-di
kernel-image-5.15.0-3-itanium-di
kernel-image-5.15.0-3-loongson-3-di
kernel-image-5.15.0-3-m68k-di
kernel-image-5.15.0-3-marvell-di
kernel-image-5.15.0-3-mips32r6-di
kernel-image-5.15.0-3-mips32r6el-di
kernel-image-5.15.0-3-mips64r6-di
kernel-image-5.15.0-3-mips64r6el-di
kernel-image-5.15.0-3-octeon-di
kernel-image-5.15.0-3-parisc-di
kernel-image-5.15.0-3-parisc64-di
kernel-image-5.15.0-3-powerpc-di
kernel-image-5.15.0-3-powerpc64-di
kernel-image-5.15.0-3-powerpc64le-di
kernel-image-5.15.0-3-riscv64-di
kernel-image-5.15.0-3-s390x-di
kernel-image-5.15.0-3-sh7751r-di
kernel-image-5.15.0-3-sh7785lcr-di
kernel-image-5.15.0-3-sparc64-di
leds-modules-5.15.0-3-arm64-di
leds-modules-5.15.0-3-armmp-di
leds-modules-5.15.0-3-marvell-di
libcpupower-dev
libcpupower1
linux-bootwrapper-5.15.0-3
linux-compiler-gcc-11-arm
linux-compiler-gcc-11-s390
linux-compiler-gcc-11-x86
linux-config-5.15
linux-cpupower (2 bugs: 0, 1, 1, 0)
linux-doc
linux-doc-5.15
linux-headers-4kc-malta
linux-headers-5.15.0-3-4kc-malta
linux-headers-5.15.0-3-5kc-malta
linux-headers-5.15.0-3-686
linux-headers-5.15.0-3-686-pae
linux-headers-5.15.0-3-alpha-generic
linux-headers-5.15.0-3-alpha-smp
linux-headers-5.15.0-3-amd64
linux-headers-5.15.0-3-arm64
linux-headers-5.15.0-3-armmp
linux-headers-5.15.0-3-armmp-lpae
linux-headers-5.15.0-3-cloud-amd64
linux-headers-5.15.0-3-cloud-arm64
linux-headers-5.15.0-3-common
linux-headers-5.15.0-3-common-rt
linux-headers-5.15.0-3-itanium
linux-headers-5.15.0-3-loongson-3
linux-headers-5.15.0-3-m68k
linux-headers-5.15.0-3-marvell
linux-headers-5.15.0-3-mckinley
linux-headers-5.15.0-3-mips32r6
linux-headers-5.15.0-3-mips32r6el
linux-headers-5.15.0-3-mips64r6
linux-headers-5.15.0-3-mips64r6el
linux-headers-5.15.0-3-octeon
linux-headers-5.15.0-3-parisc
linux-headers-5.15.0-3-parisc64
linux-headers-5.15.0-3-powerpc
linux-headers-5.15.0-3-powerpc-smp
linux-headers-5.15.0-3-powerpc64
linux-headers-5.15.0-3-powerpc64le
linux-headers-5.15.0-3-riscv64
linux-headers-5.15.0-3-rpi
linux-headers-5.15.0-3-rt-686-pae
linux-headers-5.15.0-3-rt-amd64
linux-headers-5.15.0-3-rt-arm64
linux-headers-5.15.0-3-rt-armmp
linux-headers-5.15.0-3-s390x
linux-headers-5.15.0-3-sh7751r
linux-headers-5.15.0-3-sh7785lcr
linux-headers-5.15.0-3-sparc64
linux-headers-5.15.0-3-sparc64-smp
linux-headers-5kc-malta
linux-headers-alpha-generic
linux-headers-alpha-smp
linux-headers-armmp
linux-headers-armmp-lpae
linux-headers-itanium
linux-headers-loongson-3
linux-headers-m68k
linux-headers-marvell
linux-headers-mckinley
linux-headers-mips32r6
linux-headers-mips32r6el
linux-headers-mips64r6
linux-headers-mips64r6el
linux-headers-octeon
linux-headers-parisc
linux-headers-parisc64
linux-headers-powerpc
linux-headers-powerpc-smp
linux-headers-powerpc64
linux-headers-powerpc64le
linux-headers-riscv64
linux-headers-rpi
linux-headers-rt-armmp
linux-headers-s390x
linux-headers-sh7751r
linux-headers-sh7785lcr
linux-headers-sparc64
linux-headers-sparc64-smp
linux-image-4kc-malta
linux-image-4kc-malta-dbg
linux-image-5.15.0-3-4kc-malta
linux-image-5.15.0-3-4kc-malta-dbg
linux-image-5.15.0-3-5kc-malta
linux-image-5.15.0-3-5kc-malta-dbg
linux-image-5.15.0-3-686-dbg
linux-image-5.15.0-3-686-pae-dbg
linux-image-5.15.0-3-686-pae-unsigned
linux-image-5.15.0-3-686-unsigned
linux-image-5.15.0-3-alpha-generic
linux-image-5.15.0-3-alpha-generic-dbg
linux-image-5.15.0-3-alpha-smp
linux-image-5.15.0-3-alpha-smp-dbg
linux-image-5.15.0-3-amd64-dbg
linux-image-5.15.0-3-amd64-unsigned
linux-image-5.15.0-3-arm64-dbg
linux-image-5.15.0-3-arm64-unsigned
linux-image-5.15.0-3-armmp
linux-image-5.15.0-3-armmp-dbg
linux-image-5.15.0-3-armmp-lpae
linux-image-5.15.0-3-armmp-lpae-dbg
linux-image-5.15.0-3-cloud-amd64-dbg
linux-image-5.15.0-3-cloud-amd64-unsigned
linux-image-5.15.0-3-cloud-arm64-dbg
linux-image-5.15.0-3-cloud-arm64-unsigned
linux-image-5.15.0-3-itanium
linux-image-5.15.0-3-itanium-dbg
linux-image-5.15.0-3-loongson-3
linux-image-5.15.0-3-loongson-3-dbg
linux-image-5.15.0-3-m68k
linux-image-5.15.0-3-m68k-dbg
linux-image-5.15.0-3-marvell
linux-image-5.15.0-3-marvell-dbg
linux-image-5.15.0-3-mckinley
linux-image-5.15.0-3-mckinley-dbg
linux-image-5.15.0-3-mips32r6
linux-image-5.15.0-3-mips32r6-dbg
linux-image-5.15.0-3-mips32r6el
linux-image-5.15.0-3-mips32r6el-dbg
linux-image-5.15.0-3-mips64r6
linux-image-5.15.0-3-mips64r6-dbg
linux-image-5.15.0-3-mips64r6el
linux-image-5.15.0-3-mips64r6el-dbg
linux-image-5.15.0-3-octeon
linux-image-5.15.0-3-octeon-dbg
linux-image-5.15.0-3-parisc
linux-image-5.15.0-3-parisc64
linux-image-5.15.0-3-powerpc
linux-image-5.15.0-3-powerpc-dbg
linux-image-5.15.0-3-powerpc-smp
linux-image-5.15.0-3-powerpc-smp-dbg
linux-image-5.15.0-3-powerpc64
linux-image-5.15.0-3-powerpc64-dbg
linux-image-5.15.0-3-powerpc64le
linux-image-5.15.0-3-powerpc64le-dbg
linux-image-5.15.0-3-riscv64
linux-image-5.15.0-3-riscv64-dbg
linux-image-5.15.0-3-rpi
linux-image-5.15.0-3-rpi-dbg
linux-image-5.15.0-3-rt-686-pae-dbg
linux-image-5.15.0-3-rt-686-pae-unsigned
linux-image-5.15.0-3-rt-amd64-dbg
linux-image-5.15.0-3-rt-amd64-unsigned
linux-image-5.15.0-3-rt-arm64-dbg
linux-image-5.15.0-3-rt-arm64-unsigned
linux-image-5.15.0-3-rt-armmp
linux-image-5.15.0-3-rt-armmp-dbg
linux-image-5.15.0-3-s390x
linux-image-5.15.0-3-s390x-dbg
linux-image-5.15.0-3-sh7751r
linux-image-5.15.0-3-sh7751r-dbg
linux-image-5.15.0-3-sh7785lcr
linux-image-5.15.0-3-sh7785lcr-dbg
linux-image-5.15.0-3-sparc64
linux-image-5.15.0-3-sparc64-dbg
linux-image-5.15.0-3-sparc64-smp
linux-image-5.15.0-3-sparc64-smp-dbg
linux-image-5kc-malta
linux-image-5kc-malta-dbg
linux-image-686-dbg
linux-image-686-pae-dbg
linux-image-alpha-generic
linux-image-alpha-generic-dbg
linux-image-alpha-smp
linux-image-alpha-smp-dbg
linux-image-amd64-dbg
linux-image-amd64-signed-template
linux-image-arm64-dbg
linux-image-arm64-signed-template
linux-image-armmp (1 bugs: 0, 1, 0, 0)
linux-image-armmp-dbg
linux-image-armmp-lpae
linux-image-armmp-lpae-dbg
linux-image-cloud-amd64-dbg
linux-image-cloud-arm64-dbg
linux-image-i386-signed-template
linux-image-itanium
linux-image-itanium-dbg
linux-image-loongson-3
linux-image-loongson-3-dbg
linux-image-m68k
linux-image-m68k-dbg
linux-image-marvell
linux-image-marvell-dbg
linux-image-mckinley
linux-image-mckinley-dbg
linux-image-mips32r6
linux-image-mips32r6-dbg
linux-image-mips32r6el
linux-image-mips32r6el-dbg
linux-image-mips64r6
linux-image-mips64r6-dbg
linux-image-mips64r6el
linux-image-mips64r6el-dbg
linux-image-octeon
linux-image-octeon-dbg
linux-image-parisc
linux-image-parisc-smp
linux-image-parisc64
linux-image-parisc64-smp
linux-image-powerpc
linux-image-powerpc-dbg
linux-image-powerpc-smp
linux-image-powerpc-smp-dbg
linux-image-powerpc64
linux-image-powerpc64-dbg
linux-image-powerpc64le
linux-image-powerpc64le-dbg
linux-image-riscv64
linux-image-riscv64-dbg
linux-image-rpi
linux-image-rpi-dbg
linux-image-rt-686-pae-dbg
linux-image-rt-amd64-dbg
linux-image-rt-arm64-dbg
linux-image-rt-armmp
linux-image-rt-armmp-dbg
linux-image-s390x
linux-image-s390x-dbg
linux-image-sh7751r
linux-image-sh7751r-dbg
linux-image-sh7785lcr
linux-image-sh7785lcr-dbg
linux-image-sparc64
linux-image-sparc64-dbg
linux-image-sparc64-smp
linux-image-sparc64-smp-dbg
linux-kbuild-5.15
linux-libc-dev (6 bugs: 0, 2, 4, 0)
linux-perf
linux-perf-5.15
linux-source (1 bugs: 0, 1, 0, 0)
linux-source-5.15
linux-support-5.15.0-3
loop-modules-5.15.0-3-4kc-malta-di
loop-modules-5.15.0-3-5kc-malta-di
loop-modules-5.15.0-3-686-di
loop-modules-5.15.0-3-686-pae-di
loop-modules-5.15.0-3-alpha-generic-di
loop-modules-5.15.0-3-amd64-di
loop-modules-5.15.0-3-arm64-di
loop-modules-5.15.0-3-armmp-di
loop-modules-5.15.0-3-itanium-di
loop-modules-5.15.0-3-loongson-3-di
loop-modules-5.15.0-3-m68k-di
loop-modules-5.15.0-3-marvell-di
loop-modules-5.15.0-3-mips32r6-di
loop-modules-5.15.0-3-mips32r6el-di
loop-modules-5.15.0-3-mips64r6-di
loop-modules-5.15.0-3-mips64r6el-di
loop-modules-5.15.0-3-octeon-di
loop-modules-5.15.0-3-parisc-di
loop-modules-5.15.0-3-parisc64-di
loop-modules-5.15.0-3-powerpc-di
loop-modules-5.15.0-3-powerpc64-di
loop-modules-5.15.0-3-powerpc64le-di
loop-modules-5.15.0-3-riscv64-di
loop-modules-5.15.0-3-s390x-di
loop-modules-5.15.0-3-sh7751r-di
loop-modules-5.15.0-3-sh7785lcr-di
md-modules-5.15.0-3-4kc-malta-di
md-modules-5.15.0-3-5kc-malta-di
md-modules-5.15.0-3-686-di
md-modules-5.15.0-3-686-pae-di
md-modules-5.15.0-3-alpha-generic-di
md-modules-5.15.0-3-amd64-di
md-modules-5.15.0-3-arm64-di
md-modules-5.15.0-3-armmp-di
md-modules-5.15.0-3-itanium-di
md-modules-5.15.0-3-loongson-3-di
md-modules-5.15.0-3-m68k-di
md-modules-5.15.0-3-marvell-di
md-modules-5.15.0-3-mips32r6-di
md-modules-5.15.0-3-mips32r6el-di
md-modules-5.15.0-3-mips64r6-di
md-modules-5.15.0-3-mips64r6el-di
md-modules-5.15.0-3-octeon-di
md-modules-5.15.0-3-parisc-di
md-modules-5.15.0-3-parisc64-di
md-modules-5.15.0-3-powerpc-di
md-modules-5.15.0-3-powerpc64-di
md-modules-5.15.0-3-powerpc64le-di
md-modules-5.15.0-3-riscv64-di
md-modules-5.15.0-3-s390x-di
md-modules-5.15.0-3-sh7751r-di
md-modules-5.15.0-3-sh7785lcr-di
md-modules-5.15.0-3-sparc64-di
minix-modules-5.15.0-3-4kc-malta-di
minix-modules-5.15.0-3-5kc-malta-di
minix-modules-5.15.0-3-loongson-3-di
minix-modules-5.15.0-3-marvell-di
minix-modules-5.15.0-3-octeon-di
minix-modules-5.15.0-3-sh7751r-di
minix-modules-5.15.0-3-sh7785lcr-di
mmc-core-modules-5.15.0-3-4kc-malta-di
mmc-core-modules-5.15.0-3-5kc-malta-di
mmc-core-modules-5.15.0-3-686-di
mmc-core-modules-5.15.0-3-686-pae-di
mmc-core-modules-5.15.0-3-amd64-di
mmc-core-modules-5.15.0-3-marvell-di
mmc-core-modules-5.15.0-3-powerpc-di
mmc-core-modules-5.15.0-3-powerpc64-di
mmc-core-modules-5.15.0-3-riscv64-di
mmc-modules-5.15.0-3-4kc-malta-di
mmc-modules-5.15.0-3-5kc-malta-di
mmc-modules-5.15.0-3-686-di
mmc-modules-5.15.0-3-686-pae-di
mmc-modules-5.15.0-3-amd64-di
mmc-modules-5.15.0-3-arm64-di
mmc-modules-5.15.0-3-armmp-di
mmc-modules-5.15.0-3-marvell-di
mmc-modules-5.15.0-3-riscv64-di
mouse-modules-5.15.0-3-4kc-malta-di
mouse-modules-5.15.0-3-5kc-malta-di
mouse-modules-5.15.0-3-686-di
mouse-modules-5.15.0-3-686-pae-di
mouse-modules-5.15.0-3-alpha-generic-di
mouse-modules-5.15.0-3-amd64-di
mouse-modules-5.15.0-3-itanium-di
mouse-modules-5.15.0-3-marvell-di
mouse-modules-5.15.0-3-parisc-di
mouse-modules-5.15.0-3-parisc64-di
mouse-modules-5.15.0-3-powerpc-di
mouse-modules-5.15.0-3-powerpc64-di
mouse-modules-5.15.0-3-powerpc64le-di
mtd-core-modules-5.15.0-3-4kc-malta-di
mtd-core-modules-5.15.0-3-5kc-malta-di
mtd-core-modules-5.15.0-3-686-di
mtd-core-modules-5.15.0-3-686-pae-di
mtd-core-modules-5.15.0-3-amd64-di
mtd-core-modules-5.15.0-3-arm64-di
mtd-core-modules-5.15.0-3-itanium-di
mtd-core-modules-5.15.0-3-loongson-3-di
mtd-core-modules-5.15.0-3-marvell-di
mtd-core-modules-5.15.0-3-powerpc64-di
mtd-core-modules-5.15.0-3-powerpc64le-di
mtd-core-modules-5.15.0-3-riscv64-di
mtd-core-modules-5.15.0-3-s390x-di
mtd-modules-5.15.0-3-armmp-di
mtd-modules-5.15.0-3-marvell-di
mtd-modules-5.15.0-3-riscv64-di
multipath-modules-5.15.0-3-4kc-malta-di
multipath-modules-5.15.0-3-5kc-malta-di
multipath-modules-5.15.0-3-686-di
multipath-modules-5.15.0-3-686-pae-di
multipath-modules-5.15.0-3-alpha-generic-di
multipath-modules-5.15.0-3-amd64-di
multipath-modules-5.15.0-3-arm64-di
multipath-modules-5.15.0-3-armmp-di
multipath-modules-5.15.0-3-itanium-di
multipath-modules-5.15.0-3-loongson-3-di
multipath-modules-5.15.0-3-marvell-di
multipath-modules-5.15.0-3-mips32r6-di
multipath-modules-5.15.0-3-mips32r6el-di
multipath-modules-5.15.0-3-mips64r6-di
multipath-modules-5.15.0-3-mips64r6el-di
multipath-modules-5.15.0-3-octeon-di
multipath-modules-5.15.0-3-parisc-di
multipath-modules-5.15.0-3-parisc64-di
multipath-modules-5.15.0-3-powerpc-di
multipath-modules-5.15.0-3-powerpc64-di
multipath-modules-5.15.0-3-powerpc64le-di
multipath-modules-5.15.0-3-riscv64-di
multipath-modules-5.15.0-3-s390x-di
multipath-modules-5.15.0-3-sh7751r-di
multipath-modules-5.15.0-3-sh7785lcr-di
multipath-modules-5.15.0-3-sparc64-di
nbd-modules-5.15.0-3-4kc-malta-di
nbd-modules-5.15.0-3-5kc-malta-di
nbd-modules-5.15.0-3-686-di
nbd-modules-5.15.0-3-686-pae-di
nbd-modules-5.15.0-3-alpha-generic-di
nbd-modules-5.15.0-3-amd64-di
nbd-modules-5.15.0-3-arm64-di
nbd-modules-5.15.0-3-armmp-di
nbd-modules-5.15.0-3-itanium-di
nbd-modules-5.15.0-3-loongson-3-di
nbd-modules-5.15.0-3-m68k-di
nbd-modules-5.15.0-3-marvell-di
nbd-modules-5.15.0-3-mips32r6-di
nbd-modules-5.15.0-3-mips32r6el-di
nbd-modules-5.15.0-3-mips64r6-di
nbd-modules-5.15.0-3-mips64r6el-di
nbd-modules-5.15.0-3-octeon-di
nbd-modules-5.15.0-3-parisc-di
nbd-modules-5.15.0-3-parisc64-di
nbd-modules-5.15.0-3-powerpc-di
nbd-modules-5.15.0-3-powerpc64-di
nbd-modules-5.15.0-3-powerpc64le-di
nbd-modules-5.15.0-3-riscv64-di
nbd-modules-5.15.0-3-s390x-di
nbd-modules-5.15.0-3-sh7751r-di
nbd-modules-5.15.0-3-sh7785lcr-di
nbd-modules-5.15.0-3-sparc64-di
nfs-modules-5.15.0-3-loongson-3-di
nic-modules-5.15.0-3-4kc-malta-di
nic-modules-5.15.0-3-5kc-malta-di
nic-modules-5.15.0-3-686-di
nic-modules-5.15.0-3-686-pae-di
nic-modules-5.15.0-3-alpha-generic-di
nic-modules-5.15.0-3-amd64-di
nic-modules-5.15.0-3-arm64-di
nic-modules-5.15.0-3-armmp-di
nic-modules-5.15.0-3-itanium-di
nic-modules-5.15.0-3-loongson-3-di
nic-modules-5.15.0-3-m68k-di
nic-modules-5.15.0-3-marvell-di
nic-modules-5.15.0-3-octeon-di
nic-modules-5.15.0-3-parisc-di
nic-modules-5.15.0-3-parisc64-di
nic-modules-5.15.0-3-powerpc-di
nic-modules-5.15.0-3-powerpc64-di
nic-modules-5.15.0-3-powerpc64le-di
nic-modules-5.15.0-3-riscv64-di
nic-modules-5.15.0-3-s390x-di
nic-modules-5.15.0-3-sh7751r-di
nic-modules-5.15.0-3-sh7785lcr-di
nic-modules-5.15.0-3-sparc64-di
nic-pcmcia-modules-5.15.0-3-686-di
nic-pcmcia-modules-5.15.0-3-686-pae-di
nic-pcmcia-modules-5.15.0-3-alpha-generic-di
nic-pcmcia-modules-5.15.0-3-amd64-di
nic-pcmcia-modules-5.15.0-3-powerpc-di
nic-pcmcia-modules-5.15.0-3-powerpc64-di
nic-shared-modules-5.15.0-3-4kc-malta-di
nic-shared-modules-5.15.0-3-5kc-malta-di
nic-shared-modules-5.15.0-3-686-di
nic-shared-modules-5.15.0-3-686-pae-di
nic-shared-modules-5.15.0-3-alpha-generic-di
nic-shared-modules-5.15.0-3-amd64-di
nic-shared-modules-5.15.0-3-arm64-di
nic-shared-modules-5.15.0-3-armmp-di
nic-shared-modules-5.15.0-3-itanium-di
nic-shared-modules-5.15.0-3-loongson-3-di
nic-shared-modules-5.15.0-3-m68k-di
nic-shared-modules-5.15.0-3-marvell-di
nic-shared-modules-5.15.0-3-mips32r6-di
nic-shared-modules-5.15.0-3-mips32r6el-di
nic-shared-modules-5.15.0-3-mips64r6-di
nic-shared-modules-5.15.0-3-mips64r6el-di
nic-shared-modules-5.15.0-3-octeon-di
nic-shared-modules-5.15.0-3-parisc-di
nic-shared-modules-5.15.0-3-parisc64-di
nic-shared-modules-5.15.0-3-powerpc-di
nic-shared-modules-5.15.0-3-powerpc64-di
nic-shared-modules-5.15.0-3-powerpc64le-di
nic-shared-modules-5.15.0-3-riscv64-di
nic-shared-modules-5.15.0-3-sh7751r-di
nic-shared-modules-5.15.0-3-sh7785lcr-di
nic-shared-modules-5.15.0-3-sparc64-di
nic-usb-modules-5.15.0-3-4kc-malta-di
nic-usb-modules-5.15.0-3-5kc-malta-di
nic-usb-modules-5.15.0-3-686-di
nic-usb-modules-5.15.0-3-686-pae-di
nic-usb-modules-5.15.0-3-alpha-generic-di
nic-usb-modules-5.15.0-3-amd64-di
nic-usb-modules-5.15.0-3-arm64-di
nic-usb-modules-5.15.0-3-armmp-di
nic-usb-modules-5.15.0-3-itanium-di
nic-usb-modules-5.15.0-3-loongson-3-di
nic-usb-modules-5.15.0-3-marvell-di
nic-usb-modules-5.15.0-3-octeon-di
nic-usb-modules-5.15.0-3-parisc-di
nic-usb-modules-5.15.0-3-parisc64-di
nic-usb-modules-5.15.0-3-powerpc-di
nic-usb-modules-5.15.0-3-powerpc64-di
nic-usb-modules-5.15.0-3-powerpc64le-di
nic-usb-modules-5.15.0-3-riscv64-di
nic-usb-modules-5.15.0-3-sh7751r-di
nic-usb-modules-5.15.0-3-sh7785lcr-di
nic-usb-modules-5.15.0-3-sparc64-di
nic-wireless-modules-5.15.0-3-4kc-malta-di
nic-wireless-modules-5.15.0-3-5kc-malta-di
nic-wireless-modules-5.15.0-3-686-di
nic-wireless-modules-5.15.0-3-686-pae-di
nic-wireless-modules-5.15.0-3-alpha-generic-di
nic-wireless-modules-5.15.0-3-amd64-di
nic-wireless-modules-5.15.0-3-arm64-di
nic-wireless-modules-5.15.0-3-armmp-di
nic-wireless-modules-5.15.0-3-loongson-3-di
nic-wireless-modules-5.15.0-3-octeon-di
nic-wireless-modules-5.15.0-3-powerpc-di
nic-wireless-modules-5.15.0-3-powerpc64-di
nic-wireless-modules-5.15.0-3-powerpc64le-di
nic-wireless-modules-5.15.0-3-riscv64-di
pata-modules-5.15.0-3-4kc-malta-di
pata-modules-5.15.0-3-5kc-malta-di
pata-modules-5.15.0-3-686-di
pata-modules-5.15.0-3-686-pae-di
pata-modules-5.15.0-3-alpha-generic-di
pata-modules-5.15.0-3-amd64-di
pata-modules-5.15.0-3-armmp-di
pata-modules-5.15.0-3-itanium-di
pata-modules-5.15.0-3-loongson-3-di
pata-modules-5.15.0-3-m68k-di
pata-modules-5.15.0-3-octeon-di
pata-modules-5.15.0-3-parisc-di
pata-modules-5.15.0-3-parisc64-di
pata-modules-5.15.0-3-powerpc-di
pata-modules-5.15.0-3-powerpc64-di
pata-modules-5.15.0-3-riscv64-di
pata-modules-5.15.0-3-sh7751r-di
pata-modules-5.15.0-3-sh7785lcr-di
pata-modules-5.15.0-3-sparc64-di
pcmcia-modules-5.15.0-3-686-di
pcmcia-modules-5.15.0-3-686-pae-di
pcmcia-modules-5.15.0-3-alpha-generic-di
pcmcia-modules-5.15.0-3-amd64-di
pcmcia-modules-5.15.0-3-itanium-di
pcmcia-modules-5.15.0-3-powerpc-di
pcmcia-modules-5.15.0-3-powerpc64-di
pcmcia-storage-modules-5.15.0-3-686-di
pcmcia-storage-modules-5.15.0-3-686-pae-di
pcmcia-storage-modules-5.15.0-3-amd64-di
pcmcia-storage-modules-5.15.0-3-powerpc-di
pcmcia-storage-modules-5.15.0-3-powerpc64-di
ppp-modules-5.15.0-3-4kc-malta-di
ppp-modules-5.15.0-3-5kc-malta-di
ppp-modules-5.15.0-3-686-di
ppp-modules-5.15.0-3-686-pae-di
ppp-modules-5.15.0-3-alpha-generic-di
ppp-modules-5.15.0-3-amd64-di
ppp-modules-5.15.0-3-arm64-di
ppp-modules-5.15.0-3-armmp-di
ppp-modules-5.15.0-3-itanium-di
ppp-modules-5.15.0-3-loongson-3-di
ppp-modules-5.15.0-3-m68k-di
ppp-modules-5.15.0-3-marvell-di
ppp-modules-5.15.0-3-octeon-di
ppp-modules-5.15.0-3-parisc-di
ppp-modules-5.15.0-3-parisc64-di
ppp-modules-5.15.0-3-powerpc-di
ppp-modules-5.15.0-3-powerpc64-di
ppp-modules-5.15.0-3-powerpc64le-di
ppp-modules-5.15.0-3-riscv64-di
ppp-modules-5.15.0-3-sh7751r-di
ppp-modules-5.15.0-3-sh7785lcr-di
ppp-modules-5.15.0-3-sparc64-di
rfkill-modules-5.15.0-3-686-di
rfkill-modules-5.15.0-3-686-pae-di
rfkill-modules-5.15.0-3-amd64-di
rtc-modules-5.15.0-3-octeon-di
sata-modules-5.15.0-3-4kc-malta-di
sata-modules-5.15.0-3-5kc-malta-di
sata-modules-5.15.0-3-686-di
sata-modules-5.15.0-3-686-pae-di
sata-modules-5.15.0-3-alpha-generic-di
sata-modules-5.15.0-3-amd64-di
sata-modules-5.15.0-3-arm64-di
sata-modules-5.15.0-3-armmp-di
sata-modules-5.15.0-3-itanium-di
sata-modules-5.15.0-3-loongson-3-di
sata-modules-5.15.0-3-marvell-di
sata-modules-5.15.0-3-octeon-di
sata-modules-5.15.0-3-parisc-di
sata-modules-5.15.0-3-parisc64-di
sata-modules-5.15.0-3-powerpc-di
sata-modules-5.15.0-3-powerpc64-di
sata-modules-5.15.0-3-powerpc64le-di
sata-modules-5.15.0-3-riscv64-di
sata-modules-5.15.0-3-sh7751r-di
sata-modules-5.15.0-3-sh7785lcr-di
sata-modules-5.15.0-3-sparc64-di
scsi-core-modules-5.15.0-3-4kc-malta-di
scsi-core-modules-5.15.0-3-5kc-malta-di
scsi-core-modules-5.15.0-3-686-di
scsi-core-modules-5.15.0-3-686-pae-di
scsi-core-modules-5.15.0-3-alpha-generic-di
scsi-core-modules-5.15.0-3-amd64-di
scsi-core-modules-5.15.0-3-arm64-di
scsi-core-modules-5.15.0-3-armmp-di
scsi-core-modules-5.15.0-3-itanium-di
scsi-core-modules-5.15.0-3-loongson-3-di
scsi-core-modules-5.15.0-3-m68k-di
scsi-core-modules-5.15.0-3-marvell-di
scsi-core-modules-5.15.0-3-octeon-di
scsi-core-modules-5.15.0-3-parisc-di
scsi-core-modules-5.15.0-3-parisc64-di
scsi-core-modules-5.15.0-3-powerpc-di
scsi-core-modules-5.15.0-3-powerpc64-di
scsi-core-modules-5.15.0-3-powerpc64le-di
scsi-core-modules-5.15.0-3-riscv64-di
scsi-core-modules-5.15.0-3-s390x-di
scsi-core-modules-5.15.0-3-sparc64-di
scsi-modules-5.15.0-3-4kc-malta-di
scsi-modules-5.15.0-3-5kc-malta-di
scsi-modules-5.15.0-3-686-di
scsi-modules-5.15.0-3-686-pae-di
scsi-modules-5.15.0-3-alpha-generic-di
scsi-modules-5.15.0-3-amd64-di
scsi-modules-5.15.0-3-arm64-di
scsi-modules-5.15.0-3-armmp-di
scsi-modules-5.15.0-3-itanium-di
scsi-modules-5.15.0-3-loongson-3-di
scsi-modules-5.15.0-3-m68k-di
scsi-modules-5.15.0-3-octeon-di
scsi-modules-5.15.0-3-parisc-di
scsi-modules-5.15.0-3-parisc64-di
scsi-modules-5.15.0-3-powerpc-di
scsi-modules-5.15.0-3-powerpc64-di
scsi-modules-5.15.0-3-powerpc64le-di
scsi-modules-5.15.0-3-riscv64-di
scsi-modules-5.15.0-3-s390x-di
scsi-modules-5.15.0-3-sparc64-di
scsi-nic-modules-5.15.0-3-4kc-malta-di
scsi-nic-modules-5.15.0-3-5kc-malta-di
scsi-nic-modules-5.15.0-3-686-di
scsi-nic-modules-5.15.0-3-686-pae-di
scsi-nic-modules-5.15.0-3-alpha-generic-di
scsi-nic-modules-5.15.0-3-amd64-di
scsi-nic-modules-5.15.0-3-arm64-di
scsi-nic-modules-5.15.0-3-armmp-di
scsi-nic-modules-5.15.0-3-itanium-di
scsi-nic-modules-5.15.0-3-loongson-3-di
scsi-nic-modules-5.15.0-3-octeon-di
scsi-nic-modules-5.15.0-3-powerpc-di
scsi-nic-modules-5.15.0-3-powerpc64-di
scsi-nic-modules-5.15.0-3-powerpc64le-di
scsi-nic-modules-5.15.0-3-riscv64-di
serial-modules-5.15.0-3-686-di
serial-modules-5.15.0-3-686-pae-di
serial-modules-5.15.0-3-alpha-generic-di
serial-modules-5.15.0-3-amd64-di
serial-modules-5.15.0-3-itanium-di
serial-modules-5.15.0-3-parisc-di
serial-modules-5.15.0-3-parisc64-di
serial-modules-5.15.0-3-powerpc-di
serial-modules-5.15.0-3-powerpc64-di
serial-modules-5.15.0-3-powerpc64le-di
sound-modules-5.15.0-3-4kc-malta-di
sound-modules-5.15.0-3-5kc-malta-di
sound-modules-5.15.0-3-686-di
sound-modules-5.15.0-3-686-pae-di
sound-modules-5.15.0-3-amd64-di
sound-modules-5.15.0-3-loongson-3-di
sound-modules-5.15.0-3-octeon-di
sound-modules-5.15.0-3-sh7751r-di
sound-modules-5.15.0-3-sh7785lcr-di
speakup-modules-5.15.0-3-686-di
speakup-modules-5.15.0-3-686-pae-di
speakup-modules-5.15.0-3-amd64-di
speakup-modules-5.15.0-3-loongson-3-di
speakup-modules-5.15.0-3-sh7751r-di
speakup-modules-5.15.0-3-sh7785lcr-di
squashfs-modules-5.15.0-3-4kc-malta-di
squashfs-modules-5.15.0-3-5kc-malta-di
squashfs-modules-5.15.0-3-686-di
squashfs-modules-5.15.0-3-686-pae-di
squashfs-modules-5.15.0-3-alpha-generic-di
squashfs-modules-5.15.0-3-amd64-di
squashfs-modules-5.15.0-3-arm64-di
squashfs-modules-5.15.0-3-armmp-di
squashfs-modules-5.15.0-3-itanium-di
squashfs-modules-5.15.0-3-loongson-3-di
squashfs-modules-5.15.0-3-m68k-di
squashfs-modules-5.15.0-3-marvell-di
squashfs-modules-5.15.0-3-mips32r6-di
squashfs-modules-5.15.0-3-mips32r6el-di
squashfs-modules-5.15.0-3-mips64r6-di
squashfs-modules-5.15.0-3-mips64r6el-di
squashfs-modules-5.15.0-3-octeon-di
squashfs-modules-5.15.0-3-parisc-di
squashfs-modules-5.15.0-3-parisc64-di
squashfs-modules-5.15.0-3-powerpc-di
squashfs-modules-5.15.0-3-powerpc64-di
squashfs-modules-5.15.0-3-powerpc64le-di
squashfs-modules-5.15.0-3-riscv64-di
squashfs-modules-5.15.0-3-sh7751r-di
squashfs-modules-5.15.0-3-sh7785lcr-di
squashfs-modules-5.15.0-3-sparc64-di
srm-modules-5.15.0-3-alpha-generic-di
udf-modules-5.15.0-3-4kc-malta-di
udf-modules-5.15.0-3-5kc-malta-di
udf-modules-5.15.0-3-686-di
udf-modules-5.15.0-3-686-pae-di
udf-modules-5.15.0-3-amd64-di
udf-modules-5.15.0-3-arm64-di
udf-modules-5.15.0-3-armmp-di
udf-modules-5.15.0-3-itanium-di
udf-modules-5.15.0-3-loongson-3-di
udf-modules-5.15.0-3-m68k-di
udf-modules-5.15.0-3-marvell-di
udf-modules-5.15.0-3-mips32r6-di
udf-modules-5.15.0-3-mips32r6el-di
udf-modules-5.15.0-3-mips64r6-di
udf-modules-5.15.0-3-mips64r6el-di
udf-modules-5.15.0-3-octeon-di
udf-modules-5.15.0-3-powerpc-di
udf-modules-5.15.0-3-powerpc64-di
udf-modules-5.15.0-3-powerpc64le-di
udf-modules-5.15.0-3-riscv64-di
udf-modules-5.15.0-3-s390x-di
udf-modules-5.15.0-3-sh7751r-di
udf-modules-5.15.0-3-sh7785lcr-di
udf-modules-5.15.0-3-sparc64-di
ufs-modules-5.15.0-3-sparc64-di
uinput-modules-5.15.0-3-686-di
uinput-modules-5.15.0-3-686-pae-di
uinput-modules-5.15.0-3-amd64-di
uinput-modules-5.15.0-3-arm64-di
uinput-modules-5.15.0-3-armmp-di
uinput-modules-5.15.0-3-itanium-di
uinput-modules-5.15.0-3-marvell-di
uinput-modules-5.15.0-3-powerpc-di
uinput-modules-5.15.0-3-powerpc64-di
uinput-modules-5.15.0-3-powerpc64le-di
usb-modules-5.15.0-3-4kc-malta-di
usb-modules-5.15.0-3-5kc-malta-di
usb-modules-5.15.0-3-686-di
usb-modules-5.15.0-3-686-pae-di
usb-modules-5.15.0-3-alpha-generic-di
usb-modules-5.15.0-3-amd64-di
usb-modules-5.15.0-3-arm64-di
usb-modules-5.15.0-3-armmp-di
usb-modules-5.15.0-3-itanium-di
usb-modules-5.15.0-3-loongson-3-di
usb-modules-5.15.0-3-marvell-di
usb-modules-5.15.0-3-octeon-di
usb-modules-5.15.0-3-parisc-di
usb-modules-5.15.0-3-parisc64-di
usb-modules-5.15.0-3-powerpc-di
usb-modules-5.15.0-3-powerpc64-di
usb-modules-5.15.0-3-powerpc64le-di
usb-modules-5.15.0-3-riscv64-di
usb-modules-5.15.0-3-sparc64-di
usb-serial-modules-5.15.0-3-4kc-malta-di
usb-serial-modules-5.15.0-3-5kc-malta-di
usb-serial-modules-5.15.0-3-686-di
usb-serial-modules-5.15.0-3-686-pae-di
usb-serial-modules-5.15.0-3-alpha-generic-di
usb-serial-modules-5.15.0-3-amd64-di
usb-serial-modules-5.15.0-3-arm64-di
usb-serial-modules-5.15.0-3-armmp-di
usb-serial-modules-5.15.0-3-itanium-di
usb-serial-modules-5.15.0-3-loongson-3-di
usb-serial-modules-5.15.0-3-marvell-di
usb-serial-modules-5.15.0-3-octeon-di
usb-serial-modules-5.15.0-3-parisc-di
usb-serial-modules-5.15.0-3-parisc64-di
usb-serial-modules-5.15.0-3-powerpc-di
usb-serial-modules-5.15.0-3-powerpc64-di
usb-serial-modules-5.15.0-3-powerpc64le-di
usb-serial-modules-5.15.0-3-riscv64-di
usb-serial-modules-5.15.0-3-sh7751r-di
usb-serial-modules-5.15.0-3-sh7785lcr-di
usb-serial-modules-5.15.0-3-sparc64-di
usb-storage-modules-5.15.0-3-4kc-malta-di
usb-storage-modules-5.15.0-3-5kc-malta-di
usb-storage-modules-5.15.0-3-686-di
usb-storage-modules-5.15.0-3-686-pae-di
usb-storage-modules-5.15.0-3-alpha-generic-di
usb-storage-modules-5.15.0-3-amd64-di
usb-storage-modules-5.15.0-3-arm64-di
usb-storage-modules-5.15.0-3-armmp-di
usb-storage-modules-5.15.0-3-itanium-di
usb-storage-modules-5.15.0-3-loongson-3-di
usb-storage-modules-5.15.0-3-marvell-di
usb-storage-modules-5.15.0-3-octeon-di
usb-storage-modules-5.15.0-3-parisc-di
usb-storage-modules-5.15.0-3-parisc64-di
usb-storage-modules-5.15.0-3-powerpc-di
usb-storage-modules-5.15.0-3-powerpc64-di
usb-storage-modules-5.15.0-3-powerpc64le-di
usb-storage-modules-5.15.0-3-riscv64-di
usb-storage-modules-5.15.0-3-sh7751r-di
usb-storage-modules-5.15.0-3-sparc64-di
usbip (5 bugs: 0, 5, 0, 0)
xfs-modules-5.15.0-3-4kc-malta-di
xfs-modules-5.15.0-3-5kc-malta-di
xfs-modules-5.15.0-3-686-di
xfs-modules-5.15.0-3-686-pae-di
xfs-modules-5.15.0-3-alpha-generic-di
xfs-modules-5.15.0-3-amd64-di
xfs-modules-5.15.0-3-arm64-di
xfs-modules-5.15.0-3-itanium-di
xfs-modules-5.15.0-3-loongson-3-di
xfs-modules-5.15.0-3-mips32r6-di
xfs-modules-5.15.0-3-mips32r6el-di
xfs-modules-5.15.0-3-mips64r6-di
xfs-modules-5.15.0-3-mips64r6el-di
xfs-modules-5.15.0-3-octeon-di
xfs-modules-5.15.0-3-parisc-di
xfs-modules-5.15.0-3-parisc64-di
xfs-modules-5.15.0-3-powerpc-di
xfs-modules-5.15.0-3-powerpc64-di
xfs-modules-5.15.0-3-powerpc64le-di
xfs-modules-5.15.0-3-s390x-di
xfs-modules-5.15.0-3-sh7751r-di
xfs-modules-5.15.0-3-sh7785lcr-di
xfs-modules-5.15.0-3-sparc64-di

action needed

A new upstream version is available: 5.16.2 high

A new upstream version 5.16.2 is available, you should consider packaging it.

Created: 2021-12-04 Last update: 2022-01-26 08:05

96 security issues in stretch high

There are 96 open security issues in stretch.

74 important issues:

CVE-2019-0145: Buffer overflow in i40e driver for Intel(R) Ethernet 700 Series Controllers versions before 7.0 may allow an authenticated user to potentially enable an escalation of privilege via local access.
CVE-2019-0146: Resource leak in i40e driver for Intel(R) Ethernet 700 Series Controllers versions before 2.8.43 may allow an authenticated user to potentially enable a denial of service via local access.
CVE-2019-0147: Insufficient input validation in i40e driver for Intel(R) Ethernet 700 Series Controllers versions before 7.0 may allow an authenticated user to potentially enable a denial of service via local access.
CVE-2019-0148: Resource leak in i40e driver for Intel(R) Ethernet 700 Series Controllers versions before 7.0 may allow an authenticated user to potentially enable a denial of service via local access.
CVE-2019-0149: Insufficient input validation in i40e driver for Intel(R) Ethernet 700 Series Controllers versions before 2.8.43 may allow an authenticated user to potentially enable a denial of service via local access.
CVE-2019-2213: In binder_free_transaction of binder.c, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-133758011References: Upstream kernel
CVE-2020-0030: In binder_thread_release of binder.c, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145286050References: Upstream kernel
CVE-2020-0347: In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
CVE-2021-3600:
CVE-2021-3640:
CVE-2021-3669:
CVE-2021-3752:
CVE-2021-3759:
CVE-2021-3772:
CVE-2021-3847:
CVE-2021-3864:
CVE-2021-4002:
CVE-2021-4037:
CVE-2021-4083: A read-after-free memory flaw was found in the Linux kernel's garbage collection for Unix domain socket file handlers in the way users call close() and fget() simultaneously and can potentially trigger a race condition. This flaw allows a local user to crash the system or escalate their privileges on the system. This flaw affects Linux kernel versions prior to 5.16-rc4.
CVE-2021-4095:
CVE-2021-4148:
CVE-2021-4149:
CVE-2021-4150:
CVE-2021-4155:
CVE-2021-4197:
CVE-2022-0330:
CVE-2018-10322: The xfs_dinode_verify function in fs/xfs/libxfs/xfs_inode_buf.c in the Linux kernel through 4.16.3 allows local users to cause a denial of service (xfs_ilock_attr_map_shared invalid pointer dereference) via a crafted xfs image.
CVE-2018-12929: ntfs_read_locked_inode in the ntfs.ko filesystem driver in the Linux kernel 4.15.0 allows attackers to trigger a use-after-free read and possibly cause a denial of service (kernel oops or panic) via a crafted ntfs filesystem.
CVE-2018-12930: ntfs_end_buffer_async_read in the ntfs.ko filesystem driver in the Linux kernel 4.15.0 allows attackers to trigger a stack-based out-of-bounds write and cause a denial of service (kernel oops or panic) or possibly have unspecified other impact via a crafted ntfs filesystem.
CVE-2018-12931: ntfs_attr_find in the ntfs.ko filesystem driver in the Linux kernel 4.15.0 allows attackers to trigger a stack-based out-of-bounds write and cause a denial of service (kernel oops or panic) or possibly have unspecified other impact via a crafted ntfs filesystem.
CVE-2018-13095: An issue was discovered in fs/xfs/libxfs/xfs_inode_buf.c in the Linux kernel through 4.17.3. A denial of service (memory corruption and BUG) can occur for a corrupted xfs image upon encountering an inode that is in extent format, but has more extents than fit in the inode fork.
CVE-2018-25020: The BPF subsystem in the Linux kernel before 4.17 mishandles situations with a long jump over an instruction sequence where inner instructions require substantial expansions into multiple BPF instructions, leading to an overflow. This affects kernel/bpf/core.c and net/core/filter.c.
CVE-2019-12984: A NULL pointer dereference vulnerability in the function nfc_genl_deactivate_target() in net/nfc/netlink.c in the Linux kernel before 5.1.13 can be triggered by a malicious user-mode program that omits certain NFC attributes, leading to denial of service.
CVE-2019-19036: btrfs_root_node in fs/btrfs/ctree.c in the Linux kernel through 5.3.12 allows a NULL pointer dereference because rcu_dereference(root->node) can be zero.
CVE-2019-19039: ** DISPUTED ** __btrfs_free_extent in fs/btrfs/extent-tree.c in the Linux kernel through 5.3.12 calls btrfs_print_leaf in a certain ENOENT case, which allows local users to obtain potentially sensitive information about register values via the dmesg program. NOTE: The BTRFS development team disputes this issues as not being a vulnerability because “1) The kernel provide facilities to restrict access to dmesg - dmesg_restrict=1 sysctl option. So it's really up to the system administrator to judge whether dmesg access shall be disallowed or not. 2) WARN/WARN_ON are widely used macros in the linux kernel. If this CVE is considered valid this would mean there are literally thousands CVE lurking in the kernel - something which clearly is not the case.”
CVE-2019-19377: In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image, performing some operations, and unmounting can lead to a use-after-free in btrfs_queue_work in fs/btrfs/async-thread.c.
CVE-2019-19378: In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image can lead to slab-out-of-bounds write access in index_rbio_pages in fs/btrfs/raid56.c.
CVE-2019-19449: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can lead to slab-out-of-bounds read access in f2fs_build_segment_manager in fs/f2fs/segment.c, related to init_min_max_mtime in fs/f2fs/segment.c (because the second argument to get_seg_entry is not validated).
CVE-2019-19814: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can cause __remove_dirty_segment slab-out-of-bounds write access because an array is bounded by the number of dirty types (8) but the array index can exceed this.
CVE-2019-20794: An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.
CVE-2020-12362: Integer overflow in the firmware for some Intel(R) Graphics Drivers for Windows * before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable an escalation of privilege via local access.
CVE-2020-12363: Improper input validation in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-12364: Null pointer reference in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before version Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-14304: A memory disclosure flaw was found in the Linux kernel's ethernet drivers, in the way it read data from the EEPROM of the device. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.
CVE-2020-15802: Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.
CVE-2020-26140: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26141: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The Wi-Fi implementation does not verify the Message Integrity Check (authenticity) of fragmented TKIP frames. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol.
CVE-2020-26142: An issue was discovered in the kernel in OpenBSD 6.6. The WEP, WPA, WPA2, and WPA3 implementations treat fragmented frames as full frames. An adversary can abuse this to inject arbitrary network packets, independent of the network configuration.
CVE-2020-26143: An issue was discovered in the ALFA Windows 10 driver 1030.36.604 for AWUS036ACH. The WEP, WPA, WPA2, and WPA3 implementations accept fragmented plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26145: An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration.
CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.
CVE-2020-26556: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.
CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).
CVE-2020-26559: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.
CVE-2020-26560: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.
CVE-2020-27835: A use after free in the Linux kernel infiniband hfi1 driver in versions prior to 5.10-rc6 was found in the way user calls Ioctl after open dev file and fork. A local user could use this flaw to crash the system.
CVE-2020-36385: An issue was discovered in the Linux kernel before 5.10. drivers/infiniband/core/ucma.c has a use-after-free because the ctx is reached via the ctx_list in some ucma_migrate_id situations where ucma_close is called, aka CID-f5449e74802c.
CVE-2021-28711: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28712: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28713: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28714: Guest can force Linux netback driver to hog large amounts of kernel memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is ready to process them. There are some measures taken for avoiding to pile up too much data, but those can be bypassed by the guest: There is a timeout how long the client side of an interface can stop consuming new packets before it is assumed to have stalled, but this timeout is rather long (60 seconds by default). Using a UDP connection on a fast interface can easily accumulate gigabytes of data in that time. (CVE-2021-28715) The timeout could even never trigger if the guest manages to have only one free slot in its RX queue ring page and the next package would require more than one free slot, which may be the case when using GSO, XDP, or software hashing. (CVE-2021-28714)
CVE-2021-28715: Guest can force Linux netback driver to hog large amounts of kernel memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is ready to process them. There are some measures taken for avoiding to pile up too much data, but those can be bypassed by the guest: There is a timeout how long the client side of an interface can stop consuming new packets before it is assumed to have stalled, but this timeout is rather long (60 seconds by default). Using a UDP connection on a fast interface can easily accumulate gigabytes of data in that time. (CVE-2021-28715) The timeout could even never trigger if the guest manages to have only one free slot in its RX queue ring page and the next package would require more than one free slot, which may be the case when using GSO, XDP, or software hashing. (CVE-2021-28714)
CVE-2021-29264: An issue was discovered in the Linux kernel through 5.11.10. drivers/net/ethernet/freescale/gianfar.c in the Freescale Gianfar Ethernet driver allows attackers to cause a system crash because a negative fragment size is calculated in situations involving an rx queue overrun when jumbo packets are used and NAPI is enabled, aka CID-d8861bab48b6.
CVE-2021-33033: The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
CVE-2021-33098: Improper input validation in the Intel(R) Ethernet ixgbe driver for Linux before version 3.17.3 may allow an authenticated user to potentially enable denial of service via local access.
CVE-2021-33624: In kernel/bpf/verifier.c in the Linux kernel before 5.12.13, a branch can be mispredicted (e.g., because of type confusion) and consequently an unprivileged BPF program can read arbitrary memory locations via a side-channel attack, aka CID-9183671af6db.
CVE-2021-34556: In the Linux kernel through 5.13.7, an unprivileged BPF program can obtain sensitive information from kernel memory via a Speculative Store Bypass side-channel attack because the protection mechanism neglects the possibility of uninitialized memory locations on the BPF stack.
CVE-2021-35477: In the Linux kernel through 5.13.7, an unprivileged BPF program can obtain sensitive information from kernel memory via a Speculative Store Bypass side-channel attack because a certain preempting store operation does not necessarily occur before a store operation that has an attacker-controlled value.
CVE-2021-39636: In do_ipt_get_ctl and do_ipt_set_ctl of ip_tables.c, there is a possible way to leak kernel information due to uninitialized data. This could lead to local information disclosure with system execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-120612905References: Upstream kernel
CVE-2021-39685:
CVE-2021-43975: In the Linux kernel through 5.15.2, hw_atl_utils_fw_rpc_wait in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c allows an attacker (who can introduce a crafted device) to trigger an out-of-bounds write via a crafted length value.
CVE-2021-43976: In the Linux kernel through 5.15.2, mwifiex_usb_recv in drivers/net/wireless/marvell/mwifiex/usb.c allows an attacker (who can connect a crafted USB device) to cause a denial of service (skb_over_panic).
CVE-2021-45095: pep_sock_accept in net/phonet/pep.c in the Linux kernel through 5.15.8 has a refcount leak.
CVE-2021-45469: In __f2fs_setxattr in fs/f2fs/xattr.c in the Linux kernel through 5.15.11, there is an out-of-bounds memory access when an inode has an invalid last xattr entry.

22 ignored issues:

CVE-2013-7445: The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
CVE-2018-1108: kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
CVE-2018-7273: In the Linux kernel through 4.15.4, the floppy driver reveals the addresses of kernel functions and global variables using printk calls within the function show_floppy in drivers/block/floppy.c. An attacker can read this information from dmesg and use the addresses to find the locations of kernel code and data and bypass kernel security protections such as KASLR.
CVE-2018-7754: The aoedisk_debugfs_show function in drivers/block/aoe/aoeblk.c in the Linux kernel through 4.16.4rc4 allows local users to obtain sensitive address information by reading "ffree: " lines in a debugfs file.
CVE-2019-3874: The SCTP socket buffer used by a userspace application is not accounted by the cgroups subsystem. An attacker can use this flaw to cause a denial of service attack. Kernel 3.10.x and 4.18.x branches are believed to be vulnerable.
CVE-2019-9245: In the Android kernel in the f2fs driver there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.
CVE-2019-9444: In the Android kernel in sync debug fs driver there is a kernel pointer leak due to the usage of printf with %p. This could lead to local information disclosure with system execution privileges needed. User interaction is not needed for exploitation.
CVE-2019-9453: In the Android kernel in F2FS touch driver there is a possible out of bounds read due to improper input validation. This could lead to local information disclosure with system execution privileges needed. User interaction is not needed for exploitation.
CVE-2020-0067: In f2fs_xattr_generic_list of xattr.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not required for exploitation.Product: Android. Versions: Android kernel. Android ID: A-120551147.
CVE-2020-4788: IBM Power9 (AIX 7.1, 7.2, and VIOS 3.1) processors could allow a local user to obtain sensitive information from the data in the L1 cache under extenuating circumstances. IBM X-Force ID: 189296.
CVE-2021-3506: An out-of-bounds (OOB) memory access flaw was found in fs/f2fs/node.c in the f2fs module in the Linux kernel in versions before 5.12.0-rc4. A bounds check failure allows a local attacker to gain access to out-of-bounds memory leading to a system crash or a leak of internal kernel information. The highest threat from this vulnerability is to system availability.
CVE-2017-18232: The Serial Attached SCSI (SAS) implementation in the Linux kernel through 4.15.9 mishandles a mutex within libsas, which allows local users to cause a denial of service (deadlock) by triggering certain error-handling code.
CVE-2018-12928: In the Linux kernel 4.15.0, a NULL pointer dereference was discovered in hfs_ext_read_extent in hfs.ko. This can occur during a mount of a crafted hfs filesystem.
CVE-2018-20449: The hidma_chan_stats function in drivers/dma/qcom/hidma_dbg.c in the Linux kernel 4.14.90 allows local users to obtain sensitive address information by reading "callback=" lines in a debugfs file.
CVE-2019-20908: An issue was discovered in drivers/firmware/efi/efi.c in the Linux kernel before 5.4. Incorrect access permissions for the efivar_ssdt ACPI variable could be used by attackers to bypass lockdown or secure boot restrictions, aka CID-1957a85b0032.
CVE-2020-15780: An issue was discovered in drivers/acpi/acpi_configfs.c in the Linux kernel before 5.7.7. Injection of malicious ACPI tables via configfs could be used by attackers to bypass lockdown and secure boot restrictions, aka CID-75b0cea7bf30.
CVE-2020-27777: A flaw was found in the way RTAS handled memory accesses in userspace to kernel communication. On a locked down (usually due to Secure Boot) guest system running on top of PowerVM or KVM hypervisors (pseries platform) a root like local user could use this flaw to further increase their privileges to that of a running kernel.
CVE-2021-20320:
CVE-2021-28972: In drivers/pci/hotplug/rpadlpar_sysfs.c in the Linux kernel through 5.11.8, the RPA PCI Hotplug driver has a user-tolerable buffer overflow when writing a new device name to the driver from userspace, allowing userspace to write data to the kernel stack frame directly. This occurs because add_slot_store and remove_slot_store mishandle drc_name '\0' termination, aka CID-cc7a0bb058b8.
CVE-2021-37576: arch/powerpc/kvm/book3s_rtas.c in the Linux kernel through 5.13.5 on the powerpc platform allows KVM guest OS users to cause host OS memory corruption via rtas_args.nargs, aka CID-f62f3c20647e.
CVE-2021-38207: drivers/net/ethernet/xilinx/ll_temac_main.c in the Linux kernel before 5.12.13 allows remote attackers to cause a denial of service (buffer overflow and lockup) by sending heavy network traffic for about ten minutes.
CVE-2021-38300: arch/mips/net/bpf_jit.c in the Linux kernel before 5.4.10 can generate undesirable machine code when transforming unprivileged cBPF programs, allowing execution of arbitrary code within the kernel context. This occurs because conditional branches can exceed the 128 KB limit of the MIPS architecture.

Created: 2021-02-19 Last update: 2022-01-25 22:00

30 security issues in sid high

There are 30 open security issues in sid.

30 important issues:

CVE-2013-7445: The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
CVE-2020-0347: In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
CVE-2021-3847:
CVE-2021-3864:
CVE-2021-4095:
CVE-2021-4148:
CVE-2021-4204:
CVE-2022-0330:
CVE-2018-12928: In the Linux kernel 4.15.0, a NULL pointer dereference was discovered in hfs_ext_read_extent in hfs.ko. This can occur during a mount of a crafted hfs filesystem.
CVE-2019-15213: An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver.
CVE-2019-15794: Overlayfs in the Linux kernel and shiftfs, a non-upstream patch to the Linux kernel included in the Ubuntu 5.0 and 5.3 kernel series, both replace vma->vm_file in their mmap handlers. On error the original value is not restored, and the reference is put for the file to which vm_file points. On upstream kernels this is not an issue, as no callers dereference vm_file following after call_mmap() returns an error. However, the aufs patchs change mmap_region() to replace the fput() using a local variable with vma_fput(), which will fput() vm_file, leading to a refcount underflow.
CVE-2019-16089: An issue was discovered in the Linux kernel through 5.2.13. nbd_genl_status in drivers/block/nbd.c does not check the nla_nest_start_noflag return value.
CVE-2019-19378: In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image can lead to slab-out-of-bounds write access in index_rbio_pages in fs/btrfs/raid56.c.
CVE-2019-19449: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can lead to slab-out-of-bounds read access in f2fs_build_segment_manager in fs/f2fs/segment.c, related to init_min_max_mtime in fs/f2fs/segment.c (because the second argument to get_seg_entry is not validated).
CVE-2019-19814: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can cause __remove_dirty_segment slab-out-of-bounds write access because an array is bounded by the number of dirty types (8) but the array index can exceed this.
CVE-2019-20794: An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.
CVE-2020-12362: Integer overflow in the firmware for some Intel(R) Graphics Drivers for Windows * before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable an escalation of privilege via local access.
CVE-2020-12363: Improper input validation in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-12364: Null pointer reference in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before version Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-14304: A memory disclosure flaw was found in the Linux kernel's ethernet drivers, in the way it read data from the EEPROM of the device. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.
CVE-2020-15802: Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.
CVE-2020-26140: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26142: An issue was discovered in the kernel in OpenBSD 6.6. The WEP, WPA, WPA2, and WPA3 implementations treat fragmented frames as full frames. An adversary can abuse this to inject arbitrary network packets, independent of the network configuration.
CVE-2020-26143: An issue was discovered in the ALFA Windows 10 driver 1030.36.604 for AWUS036ACH. The WEP, WPA, WPA2, and WPA3 implementations accept fragmented plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.
CVE-2020-26556: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.
CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).
CVE-2020-26559: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.
CVE-2020-26560: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.
CVE-2021-43976: In the Linux kernel through 5.15.2, mwifiex_usb_recv in drivers/net/wireless/marvell/mwifiex/usb.c allows an attacker (who can connect a crafted USB device) to cause a denial of service (skb_over_panic).

Created: 2021-02-19 Last update: 2022-01-25 22:00

74 security issues in buster high

There are 74 open security issues in buster.

61 important issues:

CVE-2020-0347: In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
CVE-2021-3493: The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivileged overlay mounts, an attacker could use this to gain elevated privileges.
CVE-2021-3640:
CVE-2021-3669:
CVE-2021-3744:
CVE-2021-3752:
CVE-2021-3759:
CVE-2021-3764:
CVE-2021-3772:
CVE-2021-3847:
CVE-2021-3864:
CVE-2021-4002:
CVE-2021-4037:
CVE-2021-4083: A read-after-free memory flaw was found in the Linux kernel's garbage collection for Unix domain socket file handlers in the way users call close() and fget() simultaneously and can potentially trigger a race condition. This flaw allows a local user to crash the system or escalate their privileges on the system. This flaw affects Linux kernel versions prior to 5.16-rc4.
CVE-2021-4095:
CVE-2021-4148:
CVE-2021-4149:
CVE-2021-4150:
CVE-2021-4155:
CVE-2021-4197:
CVE-2021-4203:
CVE-2022-0322:
CVE-2022-0330:
CVE-2019-15213: An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver.
CVE-2019-15794: Overlayfs in the Linux kernel and shiftfs, a non-upstream patch to the Linux kernel included in the Ubuntu 5.0 and 5.3 kernel series, both replace vma->vm_file in their mmap handlers. On error the original value is not restored, and the reference is put for the file to which vm_file points. On upstream kernels this is not an issue, as no callers dereference vm_file following after call_mmap() returns an error. However, the aufs patchs change mmap_region() to replace the fput() using a local variable with vma_fput(), which will fput() vm_file, leading to a refcount underflow.
CVE-2020-16120: Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef ("ovl: stack file ops"). This was fixed in kernel version 5.8 by commits 56230d9 ("ovl: verify permissions in ovl_path_open()"), 48bd024 ("ovl: switch to mounter creds in readdir") and 05acefb ("ovl: check permission to open real file"). Additionally, commits 130fdbc ("ovl: pass correct flags for opening real directory") and 292f902 ("ovl: call secutiry hook in ovl_real_ioctl()") in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da ("ovl: do not fail because of O_NOATIMEi") in kernel 5.11.
CVE-2020-26140: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26141: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The Wi-Fi implementation does not verify the Message Integrity Check (authenticity) of fragmented TKIP frames. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol.
CVE-2020-26142: An issue was discovered in the kernel in OpenBSD 6.6. The WEP, WPA, WPA2, and WPA3 implementations treat fragmented frames as full frames. An adversary can abuse this to inject arbitrary network packets, independent of the network configuration.
CVE-2020-26143: An issue was discovered in the ALFA Windows 10 driver 1030.36.604 for AWUS036ACH. The WEP, WPA, WPA2, and WPA3 implementations accept fragmented plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26145: An issue was discovered on Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration.
CVE-2020-26541: The Linux kernel through 5.8.13 does not properly enforce the Secure Boot Forbidden Signature Database (aka dbx) protection mechanism. This affects certs/blacklist.c and certs/system_keyring.c.
CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.
CVE-2020-26556: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.
CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).
CVE-2020-26559: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.
CVE-2020-26560: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.
CVE-2020-27835: A use after free in the Linux kernel infiniband hfi1 driver in versions prior to 5.10-rc6 was found in the way user calls Ioctl after open dev file and fork. A local user could use this flaw to crash the system.
CVE-2020-36310: An issue was discovered in the Linux kernel before 5.8. arch/x86/kvm/svm/svm.c allows a set_memory_region_test infinite loop for certain nested page faults, aka CID-e72436bc3a52.
CVE-2020-36322: An issue was discovered in the FUSE filesystem implementation in the Linux kernel before 5.10.6, aka CID-5d069dbe8aaf. fuse_do_getattr() calls make_bad_inode() in inappropriate situations, causing a system crash. NOTE: the original fix for this vulnerability was incomplete, and its incompleteness is tracked as CVE-2021-28950.
CVE-2020-36385: An issue was discovered in the Linux kernel before 5.10. drivers/infiniband/core/ucma.c has a use-after-free because the ctx is reached via the ctx_list in some ucma_migrate_id situations where ucma_close is called, aka CID-f5449e74802c.
CVE-2021-20317: A flaw was found in the Linux kernel. A corrupted timer tree caused the task wakeup to be missing in the timerqueue_add function in lib/timerqueue.c. This flaw allows a local attacker with special user privileges to cause a denial of service, slowing and eventually stopping the system while running OSP.
CVE-2021-20321:
CVE-2021-20322:
CVE-2021-28711: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28712: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28713: Rogue backends can cause DoS of guests via high frequency events T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Xen offers the ability to run PV backends in regular unprivileged guests, typically referred to as "driver domains". Running PV backends in driver domains has one primary security advantage: if a driver domain gets compromised, it doesn't have the privileges to take over the system. However, a malicious driver domain could try to attack other guests via sending events at a high frequency leading to a Denial of Service in the guest due to trying to service interrupts for elongated amounts of time. There are three affected backends: * blkfront patch 1, CVE-2021-28711 * netfront patch 2, CVE-2021-28712 * hvc_xen (console) patch 3, CVE-2021-28713
CVE-2021-28714: Guest can force Linux netback driver to hog large amounts of kernel memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is ready to process them. There are some measures taken for avoiding to pile up too much data, but those can be bypassed by the guest: There is a timeout how long the client side of an interface can stop consuming new packets before it is assumed to have stalled, but this timeout is rather long (60 seconds by default). Using a UDP connection on a fast interface can easily accumulate gigabytes of data in that time. (CVE-2021-28715) The timeout could even never trigger if the guest manages to have only one free slot in its RX queue ring page and the next package would require more than one free slot, which may be the case when using GSO, XDP, or software hashing. (CVE-2021-28714)
CVE-2021-28715: Guest can force Linux netback driver to hog large amounts of kernel memory T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is ready to process them. There are some measures taken for avoiding to pile up too much data, but those can be bypassed by the guest: There is a timeout how long the client side of an interface can stop consuming new packets before it is assumed to have stalled, but this timeout is rather long (60 seconds by default). Using a UDP connection on a fast interface can easily accumulate gigabytes of data in that time. (CVE-2021-28715) The timeout could even never trigger if the guest manages to have only one free slot in its RX queue ring page and the next package would require more than one free slot, which may be the case when using GSO, XDP, or software hashing. (CVE-2021-28714)
CVE-2021-28950: An issue was discovered in fs/fuse/fuse_i.h in the Linux kernel before 5.11.8. A "stall on CPU" can occur because a retry loop continually finds the same bad inode, aka CID-775c5033a0d1.
CVE-2021-38300: arch/mips/net/bpf_jit.c in the Linux kernel before 5.4.10 can generate undesirable machine code when transforming unprivileged cBPF programs, allowing execution of arbitrary code within the kernel context. This occurs because conditional branches can exceed the 128 KB limit of the MIPS architecture.
CVE-2021-39685:
CVE-2021-41864: prealloc_elems_and_freelist in kernel/bpf/stackmap.c in the Linux kernel through 5.14.9 allows unprivileged users to trigger an eBPF multiplication integer overflow with a resultant out-of-bounds write.
CVE-2021-42739: The firewire subsystem in the Linux kernel through 5.14.13 has a buffer overflow related to drivers/media/firewire/firedtv-avc.c and drivers/media/firewire/firedtv-ci.c, because avc_ca_pmt mishandles bounds checking.
CVE-2021-43389: An issue was discovered in the Linux kernel before 5.14.15. There is an array-index-out-of-bounds flaw in the detach_capi_ctr function in drivers/isdn/capi/kcapi.c.
CVE-2021-43975: In the Linux kernel through 5.15.2, hw_atl_utils_fw_rpc_wait in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c allows an attacker (who can introduce a crafted device) to trigger an out-of-bounds write via a crafted length value.
CVE-2021-43976: In the Linux kernel through 5.15.2, mwifiex_usb_recv in drivers/net/wireless/marvell/mwifiex/usb.c allows an attacker (who can connect a crafted USB device) to cause a denial of service (skb_over_panic).
CVE-2021-44733: A use-after-free exists in drivers/tee/tee_shm.c in the TEE subsystem in the Linux kernel through 5.15.11. This occurs because of a race condition in tee_shm_get_from_id during an attempt to free a shared memory object.
CVE-2021-45095: pep_sock_accept in net/phonet/pep.c in the Linux kernel through 5.15.8 has a refcount leak.
CVE-2021-45469: In __f2fs_setxattr in fs/f2fs/xattr.c in the Linux kernel through 5.15.11, there is an out-of-bounds memory access when an inode has an invalid last xattr entry.
CVE-2021-45480: An issue was discovered in the Linux kernel before 5.15.11. There is a memory leak in the __rds_conn_create() function in net/rds/connection.c in a certain combination of circumstances.

6 issues left for the package maintainer to handle:

CVE-2019-16089: (postponed; to be fixed through a stable update) An issue was discovered in the Linux kernel through 5.2.13. nbd_genl_status in drivers/block/nbd.c does not check the nla_nest_start_noflag return value.
CVE-2019-19378: (needs triaging) In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image can lead to slab-out-of-bounds write access in index_rbio_pages in fs/btrfs/raid56.c.
CVE-2019-19449: (postponed; to be fixed through a stable update) In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can lead to slab-out-of-bounds read access in f2fs_build_segment_manager in fs/f2fs/segment.c, related to init_min_max_mtime in fs/f2fs/segment.c (because the second argument to get_seg_entry is not validated).
CVE-2019-19814: (needs triaging) In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can cause __remove_dirty_segment slab-out-of-bounds write access because an array is bounded by the number of dirty types (8) but the array index can exceed this.
CVE-2019-20794: (postponed; to be fixed through a stable update) An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.
CVE-2020-15802: (postponed; to be fixed through a stable update) Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.

You can find information about how to handle these issues in the security team's documentation.

7 ignored issues:

CVE-2013-7445: The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
CVE-2018-12928: In the Linux kernel 4.15.0, a NULL pointer dereference was discovered in hfs_ext_read_extent in hfs.ko. This can occur during a mount of a crafted hfs filesystem.
CVE-2020-12362: Integer overflow in the firmware for some Intel(R) Graphics Drivers for Windows * before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable an escalation of privilege via local access.
CVE-2020-12363: Improper input validation in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-12364: Null pointer reference in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before version Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-14304: A memory disclosure flaw was found in the Linux kernel's ethernet drivers, in the way it read data from the EEPROM of the device. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.
CVE-2021-38207: drivers/net/ethernet/xilinx/ll_temac_main.c in the Linux kernel before 5.12.13 allows remote attackers to cause a denial of service (buffer overflow and lockup) by sending heavy network traffic for about ten minutes.

Created: 2021-02-19 Last update: 2022-01-25 22:00

37 security issues in bullseye high

There are 37 open security issues in bullseye.

23 important issues:

CVE-2020-0347: In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
CVE-2021-3669:
CVE-2021-3759:
CVE-2021-3847:
CVE-2021-3864:
CVE-2021-4037:
CVE-2021-4095:
CVE-2021-4148:
CVE-2021-4149:
CVE-2021-4150:
CVE-2021-4197:
CVE-2021-4204:
CVE-2022-0330:
CVE-2019-15794: Overlayfs in the Linux kernel and shiftfs, a non-upstream patch to the Linux kernel included in the Ubuntu 5.0 and 5.3 kernel series, both replace vma->vm_file in their mmap handlers. On error the original value is not restored, and the reference is put for the file to which vm_file points. On upstream kernels this is not an issue, as no callers dereference vm_file following after call_mmap() returns an error. However, the aufs patchs change mmap_region() to replace the fput() using a local variable with vma_fput(), which will fput() vm_file, leading to a refcount underflow.
CVE-2020-26140: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26142: An issue was discovered in the kernel in OpenBSD 6.6. The WEP, WPA, WPA2, and WPA3 implementations treat fragmented frames as full frames. An adversary can abuse this to inject arbitrary network packets, independent of the network configuration.
CVE-2020-26143: An issue was discovered in the ALFA Windows 10 driver 1030.36.604 for AWUS036ACH. The WEP, WPA, WPA2, and WPA3 implementations accept fragmented plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.
CVE-2020-26556: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.
CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).
CVE-2020-26559: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.
CVE-2020-26560: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.
CVE-2021-43976: In the Linux kernel through 5.15.2, mwifiex_usb_recv in drivers/net/wireless/marvell/mwifiex/usb.c allows an attacker (who can connect a crafted USB device) to cause a denial of service (skb_over_panic).

7 issues left for the package maintainer to handle:

CVE-2019-15213: (postponed; to be fixed through a stable update) An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver.
CVE-2019-16089: (postponed; to be fixed through a stable update) An issue was discovered in the Linux kernel through 5.2.13. nbd_genl_status in drivers/block/nbd.c does not check the nla_nest_start_noflag return value.
CVE-2019-19378: (needs triaging) In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image can lead to slab-out-of-bounds write access in index_rbio_pages in fs/btrfs/raid56.c.
CVE-2019-19449: (postponed; to be fixed through a stable update) In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can lead to slab-out-of-bounds read access in f2fs_build_segment_manager in fs/f2fs/segment.c, related to init_min_max_mtime in fs/f2fs/segment.c (because the second argument to get_seg_entry is not validated).
CVE-2019-19814: (needs triaging) In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can cause __remove_dirty_segment slab-out-of-bounds write access because an array is bounded by the number of dirty types (8) but the array index can exceed this.
CVE-2019-20794: (postponed; to be fixed through a stable update) An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.
CVE-2020-15802: (postponed; to be fixed through a stable update) Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.

You can find information about how to handle these issues in the security team's documentation.

7 ignored issues:

CVE-2013-7445: The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
CVE-2018-12928: In the Linux kernel 4.15.0, a NULL pointer dereference was discovered in hfs_ext_read_extent in hfs.ko. This can occur during a mount of a crafted hfs filesystem.
CVE-2020-12362: Integer overflow in the firmware for some Intel(R) Graphics Drivers for Windows * before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable an escalation of privilege via local access.
CVE-2020-12363: Improper input validation in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-12364: Null pointer reference in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before version Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-14304: A memory disclosure flaw was found in the Linux kernel's ethernet drivers, in the way it read data from the EEPROM of the device. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.
CVE-2020-24504: Uncontrolled resource consumption in some Intel(R) Ethernet E810 Adapter drivers for Linux before version 1.0.4 may allow an authenticated user to potentially enable denial of service via local access.

Created: 2021-02-19 Last update: 2022-01-25 22:00

30 security issues in bookworm high

There are 30 open security issues in bookworm.

30 important issues:

CVE-2013-7445: The Direct Rendering Manager (DRM) subsystem in the Linux kernel through 4.x mishandles requests for Graphics Execution Manager (GEM) objects, which allows context-dependent attackers to cause a denial of service (memory consumption) via an application that processes graphics data, as demonstrated by JavaScript code that creates many CANVAS elements for rendering by Chrome or Firefox.
CVE-2020-0347: In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-136658008
CVE-2021-3847:
CVE-2021-3864:
CVE-2021-4095:
CVE-2021-4148:
CVE-2021-4204:
CVE-2022-0330:
CVE-2018-12928: In the Linux kernel 4.15.0, a NULL pointer dereference was discovered in hfs_ext_read_extent in hfs.ko. This can occur during a mount of a crafted hfs filesystem.
CVE-2019-15213: An issue was discovered in the Linux kernel before 5.2.3. There is a use-after-free caused by a malicious USB device in the drivers/media/usb/dvb-usb/dvb-usb-init.c driver.
CVE-2019-15794: Overlayfs in the Linux kernel and shiftfs, a non-upstream patch to the Linux kernel included in the Ubuntu 5.0 and 5.3 kernel series, both replace vma->vm_file in their mmap handlers. On error the original value is not restored, and the reference is put for the file to which vm_file points. On upstream kernels this is not an issue, as no callers dereference vm_file following after call_mmap() returns an error. However, the aufs patchs change mmap_region() to replace the fput() using a local variable with vma_fput(), which will fput() vm_file, leading to a refcount underflow.
CVE-2019-16089: An issue was discovered in the Linux kernel through 5.2.13. nbd_genl_status in drivers/block/nbd.c does not check the nla_nest_start_noflag return value.
CVE-2019-19378: In the Linux kernel 5.0.21, mounting a crafted btrfs filesystem image can lead to slab-out-of-bounds write access in index_rbio_pages in fs/btrfs/raid56.c.
CVE-2019-19449: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can lead to slab-out-of-bounds read access in f2fs_build_segment_manager in fs/f2fs/segment.c, related to init_min_max_mtime in fs/f2fs/segment.c (because the second argument to get_seg_entry is not validated).
CVE-2019-19814: In the Linux kernel 5.0.21, mounting a crafted f2fs filesystem image can cause __remove_dirty_segment slab-out-of-bounds write access because an array is bounded by the number of dirty types (8) but the array index can exceed this.
CVE-2019-20794: An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, and resources being permanently locked up until system reboot. This can result in resource exhaustion.
CVE-2020-12362: Integer overflow in the firmware for some Intel(R) Graphics Drivers for Windows * before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable an escalation of privilege via local access.
CVE-2020-12363: Improper input validation in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-12364: Null pointer reference in some Intel(R) Graphics Drivers for Windows* before version 26.20.100.7212 and before version Linux kernel version 5.5 may allow a privileged user to potentially enable a denial of service via local access.
CVE-2020-14304: A memory disclosure flaw was found in the Linux kernel's ethernet drivers, in the way it read data from the EEPROM of the device. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.
CVE-2020-15802: Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.
CVE-2020-26140: An issue was discovered in the ALFA Windows 10 driver 6.1316.1209 for AWUS036H. The WEP, WPA, WPA2, and WPA3 implementations accept plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26142: An issue was discovered in the kernel in OpenBSD 6.6. The WEP, WPA, WPA2, and WPA3 implementations treat fragmented frames as full frames. An adversary can abuse this to inject arbitrary network packets, independent of the network configuration.
CVE-2020-26143: An issue was discovered in the ALFA Windows 10 driver 1030.36.604 for AWUS036ACH. The WEP, WPA, WPA2, and WPA3 implementations accept fragmented plaintext frames in a protected Wi-Fi network. An adversary can abuse this to inject arbitrary data frames independent of the network configuration.
CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.
CVE-2020-26556: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, able to conduct a successful brute-force attack on an insufficiently random AuthValue before the provisioning procedure times out, to complete authentication by leveraging Malleable Commitment.
CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).
CVE-2020-26559: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.
CVE-2020-26560: Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.
CVE-2021-43976: In the Linux kernel through 5.15.2, mwifiex_usb_recv in drivers/net/wireless/marvell/mwifiex/usb.c allows an attacker (who can connect a crafted USB device) to cause a denial of service (skb_over_panic).

Created: 2021-08-15 Last update: 2022-01-25 22:00

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 5.16.2-1~exp1, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 0fdf53691abbeaacdccea4ed142b1b27513c5a1d
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 23 20:42:28 2022 +0100

    [rt] Update to 5.16.2-rt19

commit bc421a0d544f47e6e570799edd7a2283e2a84f27
Merge: a87ed67aff ea069b7076
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Fri Jan 21 22:35:51 2022 +0000

    Merge branch 'waldi/build-depend-pahole' into 'master'
    
    Build-depend on pahole after rename from dwarves
    
    See merge request kernel-team/linux!441

commit ea069b70768184f77083b87e10d4c38b92faa827
Author: Bastian Blank <waldi@debian.org>
Date:   Fri Jan 21 14:31:05 2022 +0100

    Build-depend on pahole after rename from dwarves

commit a87ed67affcc44de1b210be077054b684d1746f7
Merge: 6a106c01f7 ff025fbc65
Author: Bastian Blank <waldi@debian.org>
Date:   Fri Jan 21 13:30:00 2022 +0000

    Merge branch 'salsa-ci' into 'master'
    
    Add CI config using some of the common pipeline and a new build profile
    
    See merge request kernel-team/linux!438

commit 6a106c01f7f0f4ef416f6a5ed2ee0985eab3eff7
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Fri Jan 21 10:02:32 2022 +0100

    Add bug closer for #1004095
    
    Gbp-Dch: Ignore

commit ea7f5e67f4ef6e9aab96c38fa558c0b23889737b
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Fri Jan 21 09:38:07 2022 +0100

    [rt] Update to 5.16.2-rt18

commit c2759090b87b53d0d2c5956a75b6d91979231de1
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Fri Jan 21 09:07:25 2022 +0100

    Update to 5.16.2
    
    Drop patches applied upstream

commit c366c7f09b9a0ed8dad73f75d9d90aa8079f9479
Merge: b4ed8c0a97 68ba154949
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Fri Jan 21 09:02:39 2022 +0100

    Merge tag 'debian/5.15.15-1'
    
    Release linux (5.15.15-1).

commit b4ed8c0a9775b504802817911a8f3018216ceeb9
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Thu Jan 20 00:15:35 2022 +0100

    [riscv64] Add support for SBI SRST extension: update patch URL to point to Linus' tree

commit ff025fbc654b0275059dfea56345f54cd1a7fd4a
Author: Ben Hutchings <benh@debian.org>
Date:   Tue Jan 18 22:09:08 2022 +0100

    d/salsa-ci.yml: Use per-release cache of orig tarballs
    
    Caching orig tarballs saves several minutes in the extract-source job,
    and will reduce load on git.kernel.org.

commit 68ba154949235a96f5a686ea3d96b0afe83b87a9
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Tue Jan 18 22:31:03 2022 +0100

    Prepare to release linux (5.15.15-1).

commit 15c8ece90296883203a877c1e21bcfb270ed5f80
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Mon Jan 17 17:35:22 2022 +0100

    vfs: fs_context: fix up param length parsing in legacy_parse_param (CVE-2022-0185)

commit 0f990afe2b8a605cf05f97a20edcd5ae58e5ba2d
Merge: ff3f447221 b545a49295
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Sun Jan 16 21:27:59 2022 +0000

    Merge branch 'benh/lintian-fixes' into 'master'
    
    Fix some lintian errors and warnings
    
    See merge request kernel-team/linux!439

commit ff3f44722151609d8ef2e30b1becf0b2283c0bd3
Merge: 3bf8297b89 4248b8391d
Author: Bastian Blank <waldi@debian.org>
Date:   Sun Jan 16 21:23:27 2022 +0000

    Merge branch 'benh/upstream-is-git' into 'master'
    
    Embrace Git as the only useful upstream
    
    See merge request kernel-team/linux!436

commit b6aa44f700f99f87d952c8b32341220e0e49ccec
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 10 20:29:50 2022 +0100

    bpftool, objtool, usbip: Always build with V=1 so blhc can check them
    
    We have to use the terse build option for CI builds, but blhc needs to
    see full compiler command lines to be useful.  Ignore terse when
    building these.

commit 9d021749ce816421e67d775bdaaae074484a8fc2
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 10 19:32:10 2022 +0100

    d/rules, d/salsa-ci.yml: Enable blhc, ignoring terse output
    
    blhc wants to see complete compiler command lines and complains when
    it sees the summary lines that appear with the terse option.  However,
    currently the terse option mostly affects the output for builds of
    kernel code, which need different hardening options that blhc doesn't
    know about.
    
    So add a line to the log when building with terse, telling blhc to
    ignore the CC, CCLD, LD, and lINK summary lines.

commit dc40ae91dc1bb0dd3e8c69c26dc2f9e926df7b58
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 14:40:47 2022 +0100

    d/salsa-ci.yml: Run kconfigeditor2 as kconfig static check
    
    Run kconfigeditor2's process.py script and treat any error output
    as a failure.

commit 468ed7d734cf356958460313c37d8086f08a6ecd
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 14:07:24 2022 +0100

    d/salsa-ci.yml, d/tests/python: Only run static checks in CI
    
    From bug report <https://bugs.debian.org/992798> on initramfs-tools:
    > Static analysis tools are intended to run on source code, while
    > autopkgtest is intended to run against installed packages, where source
    > code is in principle not relevant; we want to know whether the binary
    > packages, as provided in the Debian archive, work correctly. In our
    > opinion running this type of tools as integration tests in autopkgtest,
    > or even as build-time tests is Wrong™, and should not be done.
    
    Stop running pycodestyle and pyflakes3 under autopkgtest.  Add a job
    to the Salsa CI configuration that runs them.

commit b81a081ffc107442553a56eeca51f0a37ab0a814
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 3 02:15:09 2022 +0100

    d/salsa-ci.yml: Add CI config using some of the common pipeline
    
    - The common salsa-ci pipeline provides a lot of useful tests, but
      with the current limits of Salsa it does not work for large
      packages (see salsa-ci-team/pipeline#195).  This pipeline avoids
      that issue by putting packed source in artifacts instead of
      unpacked.
    
    - The current shared runners on Salsa are quite slow, so we can't
      afford to run multiple builds or even a complete default build.
      Instead this uses the pkg.kernel.quick profile and disables the
      features that are currently broken in that profile.
    
    - Although the shared runners have 2 CPUs, I found that building with
      parallel=4 seemed to be slightly faster than the default parallel=2.
    
    - Each job's log is also limited to 4 MiB, whereas a verbose build
      log for the pkg.linux.quick profile is around 28 MiB.  So this uses
      the terse build option and excludes the blhc test which treats that
      as an error.

commit 00db919943725f2fd91356595c1d9beeb37c9c95
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 3 01:29:18 2022 +0100

    Introduce pkg.linux.quick build profile for quicker CI builds
    
    This build profile should greatly reduce build time while still
    providing good code coverage:
    
    - At most one specified kernel flavour is built.  (This currently
      breaks building of udebs and signed code templates, which will need
      to be fixed.)  This saves a lot of time where there are multiple
      flavours, but does mean there is zero coverage for featuresets.
    
      I wanted to build the default flavour, but Salsa's shared runners
      are extremely slow and for amd64 this turned out to take more than
      the time limit of 3 hours (vs < 20 min on a local build machine).
      So the quick flavour is initially defined for amd64 and arm64 as the
      repsective cloud flavours.
    
    - Debug information is disabled for the kernel.  This saves about
      25% of the default build time in a local build.
    
    - linux-doc and linux-source packages are not built.  This saves
      about 20% of the default build time in a local build.
    
    - All binary packages are compressed with gzip.  This saves about
      1% of the default build time in a local build.
    
    The combined effect on a local amd64 build is to reduce build time
    (without ccache) from around 80 minutes to 8 minutes.
    
    Salsa's shared runners still take around 80 minutes to build this,
    which is comfortably under the 3 hour limit but still quite slow.

commit a4c612e9e09a963937ea162cff716eb3f6d68c3a
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 3 01:25:21 2022 +0100

    d/bin/gencontrol.py, d/rules.real: Replace DEBUG variable with if_package
    
    I want to be able to control the generation with debug packages with a
    build profile.  To allow for this, use the if_package macro in
    rules.real instead of a DEBUG variable passed down from rules.gen.

commit 38c60fca91327541ae2d33d03681476013b62098
Author: Ben Hutchings <benh@debian.org>
Date:   Mon Jan 3 01:03:03 2022 +0100

    d/bin/gencontrol.py, d/lib/python: Use classes for build restriction formulae
    
    This produces a mostly identical debian/control, except that profile
    names are now sorted within a restriction list.  This is not a problem
    as they are order-independent.

commit 3cec071228fb7633ccfa4ee7d34bb984e5e07a78
Author: Ben Hutchings <benh@debian.org>
Date:   Fri Jan 7 04:02:26 2022 +0100

    d/rules: Filter out -s option so that Kbuild is not silent
    
    dpkg-buildpackage now passes the -s option to make if
    DEB_BUILD_OPTIONS contains terse, but that triggers Kbuild to turn off
    progress messages completely.  This doesn't seem to match the intended
    meaning of the option, so filter out -s.
    
    It would be preferable to do this in debian/rules.real, so the -s flag
    is still in effect for debian/rules and debian/rules.gen, but when I
    tried that the -j and --job-server options were lost so the build
    became serial.
    
    It's also necessary to use 'override' when replacing MAKEFLAGS, though
    not when appending.

commit 9bbf3331de0772f65605ed7d545e086749474aa4
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 16 01:30:00 2022 +0100

    d/rules: Tell blhc to ignore kernel compilation
    
    Kernel code needs different hardening options that blhc doesn't know
    about.

commit 19cbe45130eb395e7c22b27a8f57232d28fd96ef
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 21:06:40 2022 +0100

    d/rules: Tell blhc to ignore missing flags for perf-read-vdso* helpers
    
    The perf-read-vdso* programs are built for different architectures,
    without standard flags, but are not exposed to untrusted input.

commit 573af22ecfeee01ed474bc62e4520a96afa09f1d
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 23:00:23 2022 +0100

    tools/perf: Fix missing LDFLAGS for some programs

commit 70ec363cfd779d36b1180eb0cb686fc6620b6955
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 22:31:44 2022 +0100

    libapi: Define _FORTIFY_SOURCE as 2, not empty

commit b467354cace3ccfcd98b8591fb6e2d3ae2c598c7
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 21:59:33 2022 +0100

    tools/perf: Define DEBUG=0 for sub-make so libapi doesn't use wrong flags
    
    DEBUG=0 is the default for perf itself (set in Makefile.config), but
    it's not passed down to libapi and it uses the wrong compiler options
    unless it's explicitly set.

commit cf5238aa51bb6611bb7393ea6ec5f6f7c1a37711
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 22:08:27 2022 +0100

    objtool: Build with standard CFLAGS and CPPFLAGS

commit f9800fc778242b7caea469e2cc53f618e6a28d24
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 20:30:54 2022 +0100

    usbip: Build with standard CPPFLAGS
    
    usbip does not ignore CPPFLAGS, but we were wrongly setting it from
    the standard CFLAGS!

commit 25b5c5846dd6572034a4f474e639a04bb36e2bf0
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 20:25:34 2022 +0100

    cpupower: Build with standard CPPFLAGS
    
    cpupower ignores the given CPPFLAGS, so add them to CFLAGS.

commit b101828c0ebb7430f47a4e5210e97c2293ae0e52
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 20:20:07 2022 +0100

    linux-kbuild: Build modpost with standard CPPFLAGS

commit fc2f944bc63e84ca72b6ddbdf80a39f22d1c07ea
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 19:56:29 2022 +0100

    d/rules.real: Define KBUILD_HOST{C,LD}FLAGS for sub-make
    
    This fixes missing hardening options for some of user-space (43 out of
    131 blhc errors).

commit b545a4929591c67a854cd268cf12a34145b1b8a0
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 21:24:39 2022 +0100

    d/tests/selftests: Use $AUTOPKGTEST_TMP instead of $ADTTMP
    
    The latter is deprecated, according to lintian.

commit b49738980a0fc560d9fe4ce5defb60bd65bf9b90
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 21:23:24 2022 +0100

    debian/copyright: Update for removed and renamed source files

commit b075afc65e140c1461103b08f59437e7c75ef38a
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 21:22:55 2022 +0100

    d/copyright: Fix license name with spaces in it
    
    "GPL2+ or X11" is parsed as two separate licenses which each require
    their own text.  But we have a combined license text for this.
    Replace the spaces with hyphens.

commit 85be660d2bb504fe2e85c4ac024d5e171ba764e7
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 20:48:56 2022 +0100

    lintian: Refresh lintian-overrides
    
    - source: Update filename for the first override of
      license-problem-gfdl-invariants.  Drop the second override as it's
      no longer detected.
    - source: Add overrides for field-too-long in the .dsc file, as this
      is not a bug.
    - source: Add overrides for source-contains-prebuilt-windows-binary,
      as these are test cases for perf and their source is provided.
    - hyperv-daemons: Add override for maintainer-script-calls-systemctl;
      our use of systemctl is properly conditional on systemd running.
    - libcpupower1: Add override for
      symbols-file-contains-debian-revision: we really have changed
      symbols in Debian revisions, and those were experimental uploads
      that won't get backported so we don't need to append ~.
    - linux-image-<abiname><flavour>-dbg:
      Replace shlib-without-PT_GNU_STACK-section with the new name
      shared-library-lacks-stack-section.
    - [amd64] linux-image-<abiname><flavour>-dbg: Drop override for
      binary-from-other-architecture on vdso32.so, which is now allowed.
    - linux-image-<flavour>-dbg: Drop override for
      debug-package-should-be-priority-extra, which has been removed.
    - linux-perf-<version>: Add override for
      shared-library-lacks-prerequisites in plugins.  Some of these only
      need symbols from libtraceevent, which loads them and should not
      have a NEEDED entry.
    - linux-perf-<version>: Drop override of
      binary-from-other-architecture for perf-read-vdso32, and apply the
      override for perf-read-vdsox32 only on amd64.

commit 4248b8391d8544534bb146cc7127491306a323dc
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 13:11:28 2022 +0100

    d/bin/genorig.py, d/README.source: Add support for remote upstream repos
    
    The common salsa-ci pipeline uses origtargz to download a tarball
    from Debian or upstream (in the latter case via uscan).  Ideally
    we could do that too, even if we can't currently use the whole of
    that pipeline.
    
    Unfortunately, in our configuration uscan will compress the entire
    upstream source twice (bug #1003251), so genorig.py is still
    preferable.
    
    To avoid duplicating version logic in salsa-ci.yml, extend genorig.py
    to support remote repositories.  In case the repository path is
    remote, make a temporary shallow clone of it and export from that.

commit 7c3ba8a71a9e1599c78bb66c47826dd2ccddccb9
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 13:10:12 2022 +0100

    d/bin/genorig.py, d/README.source: Only support Git as upstream
    
    genorig.py still supports using a Git tag, a tarball, or a tarball
    and patch as upstream.  However:
    
    - I don't think anyone on the kernel team uses upstream tarballs any
      more, so this is not being tested
    - We never automated signature verification for tarballs and patches
    - Upstream release candidates don't even have tarballs
    - I also just switched debian/watch over to Git tags, so this will
      ensure Git tags are consistently used as upstream

commit 2d472745c08eb0a970f0655642fe4e789dba562e
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 13:09:02 2022 +0100

    d/watch: Rewrite to find all upstream versions through Git
    
    Currently only the versions listed on the front of www.kernel.org
    are found, and release candidates are specifically excluded.
    
    Just changing the regexp to include release candidates won't work,
    because:
    
    - The directory name inside an rc tarball contains "-rc" whereas
      "debian/rules orig" expects "~rc", though we could fix that.
    - The tarball links for release candidates are actually served by
      CGit, and there are no signatures provided for them.
    
    Changing the URL to https://www.kernel.org/pub/linux/kernel/v5.x/
    would alllow finding tarballs for all stable releases, but release
    candidates are not present there.
    
    The only way to get all versions *with* signatures is through Git.
    Unfortunately, in this mode uscan will compress the entire upstream
    source twice (bug #1003251), so genorig.py is still preferable.

commit 894bb9cdb9816ec87932d842e4acf26888b649af
Author: Ben Hutchings <benh@debian.org>
Date:   Thu Jan 6 04:28:07 2022 +0100

    d/bin/git-tag-gpg-wrapper, debian/upstream: Use ASCII-armored keyring
    
    uscan now insists on having an ASCII-armored keyring signing-key.asc
    and forcibly converts the binary keyring signing-key.pgp if present.
    
    Give in to the inevitable.  However, rather than using a single
    ASCII-armored blob, use a series of public key blocks commented with
    the name and key ID.

commit 59205dee669933e6186d4ace3e0e87d983f997ca
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 16 13:49:55 2022 +0100

    Update to 5.15.15
    
    Drop patches applied upstream
    
    Cleanup debian/changelog file

commit 3bf8297b894f87bb699a4f9ce053b1cc3761bcf6
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 16 09:42:06 2022 +0100

    Update to 5.16.1

commit 3bdea70aee4d5b35ea586b0722282c4d430a5a87
Merge: 5dda507cad 7455a8585e
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Fri Jan 14 23:27:49 2022 +0000

    Merge branch 'benh/rt-trace-hist' into 'master'
    
    [rt] trace: Enable OSNOISE_TRACER, TIMERLAT_TRACER, HIST_TRIGGERS
    
    See merge request kernel-team/linux!437

commit 5dda507cadf1d0064d0dc478f7931abcb7d95fff
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 00:15:05 2022 +0100

    debian/changelog: Really move the last addition to the open entry

commit b908d5586cf049ec9237b1da41044074ab0d1c9a
Merge: 8ddf980d85 b84e223ca8
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 15 00:09:28 2022 +0100

    Merge branch 'mips-boston-disable-its' into 'master'
    
    MIPS: renew Boston disable its patches
    
    See merge request kernel-team/linux!423
    
    [bwh: Move the new changelog additions to the open entry]

commit 46025c1379e99dabec114323bba6af598e5ac1d0
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Fri Jan 14 05:58:33 2022 +0100

    bpf: Fix out of bounds access from invalid *_or_null type verification (CVE-2022-23222)

commit 590af0637e24a07811d81bfa90df6a6753d10bd2
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Thu Jan 13 23:40:52 2022 +0100

    Update to 5.15.14
    
    Refresh "radeon, amdgpu: Firmware is required for DRM and KMS on R600 onward"
    
    Add CVE id reference for CVE-2021-4155
    
    Add CVE id reference for CVE-2021-45095
    
    Add CVE id reference for CVE-2021-4197
    
    Cleanup debian/changelog file

commit 8ddf980d85bd632364db39094b36faf1f396793c
Merge: 8fb8446a46 d43df87cd5
Author: Aurelien Jarno <aurel32@debian.org>
Date:   Tue Jan 11 23:27:06 2022 +0000

    Merge branch 'riscv64-srst' into 'master'
    
    [riscv64] Add support for SBI SRST extension
    
    See merge request kernel-team/linux!434

commit d43df87cd578ea9a03d48d49c6a8bae48650e076
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Tue Jan 11 22:15:50 2022 +0100

    [riscv64] Add support for SBI SRST extension

commit b84e223ca8a62acbe9ba72a28fca59a8a6cf027c
Author: YunQiang Su <syq@debian.org>
Date:   Mon Nov 15 12:33:39 2021 +0800

    MIPS: renew Boston disable its patches
    
    1. remove zload-$(CONFIG_MIPS_GENERIC): which will break qemu.
    2. We can just remove vmlinux.gz.itb from all-$(CONFIG_MIPS_GENERIC)

commit 8fb8446a462bfebd9360d243663a32796dc82a0a
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Mon Jan 10 06:38:03 2022 +0100

    Update to 5.16
    
    Refresh "radeon, amdgpu: Firmware is required for DRM and KMS on R600 onward"

commit bc04c488b6d9a6829fc3ea57b6386c2155adfa1f
Merge: f073a9fa90 34f83ca68e
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Sun Jan 9 23:16:35 2022 +0000

    Merge branch 'benh/armhf-modularise-media' into 'sid'
    
    [armhf] media: Set MEDIA_SUPPORT=m so drivers are no longer built-in
    
    See merge request kernel-team/linux!430

commit 6b1107a58f7b9d397fb813f29bdb9ba1ec823f2f
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 9 20:45:58 2022 +0100

    debian/config: Clean up with the help of kconfigeditor2
    
    Gbp-Dch: Ignore

commit 9682dc5df90787f778a39338a4010e3aa8afecd5
Merge: c8fdfd417f d8b28acb9d
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 9 19:44:24 2022 +0000

    Merge branch 'realtek-802.11ax' into 'master'
    
    Realtek 802.11ax wireless chips support
    
    See merge request kernel-team/linux!435

commit 7455a8585e1a68f50efe933fc586c1396e4adbc2
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 16:05:42 2022 +0100

    [rt] trace: Enable OSNOISE_TRACER, TIMERLAT_TRACER, HIST_TRIGGERS
    
    The upstream trace subsystem now has a generic histogram facility,
    enabled by CONFIG_HIST_TRIGGERS.  Together with the added tracers,
    this should provide a replacement for the
    CONFIG_{MISSED_TIMER_OFFSETS,WAKEUP_LATENCY}_HIST options we used to
    enable.

commit c8fdfd417faff2d096a71d6e94e5082e4b5f31a9
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 9 16:20:23 2022 +0100

    debian/README.source: Tag signatures are automatically verified
    
    genorig.py has been checking tag signatures for over 5 years, so stop
    telling people to do it again.  This is not yet implemented for tarballs
    and we should probably drop support for tarballs entirely.

commit f073a9fa90ddd6360504733d896fb0a99cca2efd
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 9 15:20:12 2022 +0100

    Update to 5.15.13
    
    Drop patches applied upstream
    
    Cleanup debian/changelog file

commit 147f7fdd8704c5b149b0bfe37d7b7a8f278d7998
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 9 14:42:57 2022 +0100

    drm/nouveau: wait for the exclusive fence after the shared ones
    
    Closes: #1000681

commit d8b28acb9df528159335baaa96de95a6eb694dbc
Author: Vincent Blut <vincent.debian@free.fr>
Date:   Sat Jan 8 14:16:34 2022 +0100

    drivers/net/wireless/realtek/rtw89: Enable RTW89 and RTW89_8852AE as modules

commit e80ae6067ae9068475e349e521694f96a3934b59
Author: Ben Hutchings <benh@debian.org>
Date:   Thu Jan 6 00:19:39 2022 +0100

    debian/changelog: Set current entry's distribution to UNRELEASED
    
    I don't expect this version to be released immediately, so set it to
    UNRELEASED to avoid confusion.

commit 656d7dbb2874e2d8bf67c0603c826f3028a5dcca
Merge: 218c07cbb6 47320f683c
Author: Ben Hutchings <ben@decadent.org.uk>
Date:   Tue Jan 4 14:57:52 2022 +0000

    Merge branch 'bug-983757' into 'master'
    
    Multiarchify python build-depends. (Closes: #983757)
    
    See merge request kernel-team/linux!432

commit 47320f683c8dd137361ee2397d5f627be76c1f54
Author: Ben Hutchings <benh@debian.org>
Date:   Tue Jan 4 15:44:23 2022 +0100

    linux-perf: Fix detection of libperl and libpython in cross-build
    
    Currently perf is picking up the native compiler flags for libperl and
    libpython.  This happens to work for some cross-builds with matched
    word size, but isn't generally going to work.
    
    * For libperl, set environment variable PERL5LIB so that
      ExtUtils::Embed picks up the cross-build configuration
    * For libpython, set PYTHON_CONFIG to the appropriately prefixed
      version of python3-config

commit 35dbd841b4d8bb4f45c63d966574d0c517373161
Author: Helmut Grohne <helmut@subdivi.de>
Date:   Mon Jan 3 12:58:43 2022 +0100

    Multiarchify python build-depends. (Closes: #983757)

commit 396b7d1eb2da978dc2e4d12db4e5349f6280d03b
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Mon Jan 3 22:49:58 2022 +0100

    drivers/infiniband/hw/irdma: Enable INFINIBAND_IRDMA as module
    
    Closes: #1003082

commit 0dbef59526d3fb03f0a390b6803f2edac57c042c
Merge: 4c86c67de7 9c2e2c5f8b
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 2 21:25:45 2022 +0100

    Merge branch 'mr-salsa-374' into sid
    
    Without CONFIG_CAN_MCP251X=m, MCP251X based CAN controllers are
    unusable. This is often found paired with single board computers like
    the RPi, ODROID, UDOO, Toradex, etc.
    
    See merge request kernel-team/linux!374

commit 34f83ca68e84c94ec6214b0b29c4604f7260caa6
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 1 03:36:52 2022 +0100

    [armhf] media: Set MEDIA_SUPPORT=m so drivers are no longer built-in
    
    The top-level config has CONFIG_MEDIA_SUPPORT=m, but the armmp and
    armmp-lpae flavours have always overridden it to =y.  That results in
    CONFIG_MEDIA_TUNER=y.  Together with CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
    this in turns results in the V4L2 and DVB cores and many tuner drivers
    being built-in.
    
    This seems to be just a mistake, as there's no need to have these
    drivers built in.  Remove the override.

commit 4c86c67de7e0301752b1c750f669ec4c8e7a170e
Author: Salvatore Bonaccorso <carnil@debian.org>
Date:   Sun Jan 2 11:33:36 2022 +0100

    Add Debian bug closer for #1001559

commit 55d25909384e31ebafd75e802aa1be1a6bbb6eac
Author: Ben Hutchings <benh@debian.org>
Date:   Sun Jan 2 04:43:52 2022 +0100

    debian/control: Add version to libopencsd-dev build-dependency
    
    When backporting to bullseye, I found that perf can no longer be built
    with its version of opencsd.  The minimum version was bumped to 1.0.0
    in 5.12 and then again to 1.1.1 in 5.14, but perf would quietly
    disable use of opencsd if it was too old.  Starting with 5.15 this is
    instead a fatal error.
    
    So put the current minimum version in Build-Depends.

commit 4d1c5fdf938761380138d9d270aabc5d387b5940
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 1 22:10:50 2022 +0100

    [rt] Update to 5.15.10-rt24
    
    A few of the patches look different, as they have been regenerated
    from git.  But there don't seem to be any functional changes.

commit 54a44a3b14b2254d55027f38adf2f4b28ec103db
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 1 21:50:21 2022 +0100

    [rt] Add new signing key for Clark Williams

commit 526ba0ed6f7f7eeb235d633c30a71f01b469c5d3
Author: Ben Hutchings <benh@debian.org>
Date:   Sat Jan 1 17:22:21 2022 +0100

    Update to 5.15.12
    
    * Drop changes applied on the stable branch
    * Bump ABI to 3, as there are a few ABI changes that I'm not going to
      spend the time to avoid
    * wait: Export new function __wake_up_pollfree() needed by binder

commit 9c2e2c5f8b788addfbefc568dc7e02a4b3d8e1de
Author: Andrew Balmos <andrew@balmos.org>
Date:   Fri Jul 9 15:00:38 2021 +0000

    net/can: Enable CONFIG_CAN_MCP251X as module

Created: 2022-01-04 Last update: 2022-01-26 13:30

Multiarch hinter reports 1 issue(s) normal

There are issues with the multiarch metadata for this package.

libcpupower1 could be marked Multi-Arch: same

Created: 2022-01-21 Last update: 2022-01-26 13:06

18 bugs tagged patch in the BTS normal

The BTS contains patches fixing 18 bugs (20 if counting merged bugs), consider including or untagging them.

Created: 2021-08-14 Last update: 2022-01-26 13:01

Depends on packages which need a new maintainer normal

The packages that linux depends on which need a new maintainer are:

dh-exec (#851746)
- Build-Depends: dh-exec

Created: 2019-11-22 Last update: 2022-01-26 11:02

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2021-04-16 Last update: 2022-01-26 08:07

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2021-03-20 Last update: 2021-10-14 18:58

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.0 instead of 4.2.0).

Created: 2017-12-02 Last update: 2022-01-19 12:06

testing migrations

This package will soon be part of the auto-perl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
This package will soon be part of the perl-5.34 transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2022-01-24] linux 5.15.15-1 MIGRATED to testing (Debian testing watch)
[2022-01-20] Accepted linux 5.10.92-1 (source) into stable-security->embargoed, stable-security (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2022-01-19] Accepted linux 5.15.15-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2022-01-06] Accepted linux 5.15.5-2~bpo11+1 (source) into bullseye-backports, bullseye-backports (Debian FTP Masters) (signed by: Ben Hutchings)
[2022-01-03] Accepted linux 5.16~rc8-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-28] linux 5.15.5-2 MIGRATED to testing (Debian testing watch)
[2021-12-27] Accepted linux 5.16~rc7-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-22] Accepted linux 5.16~rc6-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-18] Accepted linux 5.15.5-2 (source) into unstable (Salvatore Bonaccorso)
[2021-12-16] Accepted linux 4.9.290-1 (source) into oldoldstable, oldoldstable (Debian FTP Masters) (signed by: Ben Hutchings)
[2021-12-15] Accepted linux 5.16~rc5-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-09] Accepted linux 5.10.84-1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-08] Accepted linux 5.16~rc4-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-12-03] linux 5.15.5-1 MIGRATED to testing (Debian testing watch)
[2021-11-29] Accepted linux 5.16~rc3-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-11-26] Accepted linux 5.15.5-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-11-26] linux 5.15.3-1 MIGRATED to testing (Debian testing watch)
[2021-11-20] Accepted linux 5.16~rc1-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-11-19] Accepted linux 5.15.3-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-11-15] Accepted linux 5.15.2-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-11-15] linux 5.14.16-1 MIGRATED to testing (Debian testing watch)
[2021-11-07] Accepted linux 5.15.1-1~exp1 (source) into experimental (Salvatore Bonaccorso)
[2021-11-04] Accepted linux 5.15-1~exp1 (source) into experimental, experimental (Debian FTP Masters) (signed by: Bastian Blank)
[2021-11-03] Accepted linux 5.14.16-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-10-20] Accepted linux 5.10.70-1~bpo10+1 (source) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Ben Hutchings)
[2021-10-15] Accepted linux 5.14.9-2~bpo11+1 (source) into bullseye-backports, bullseye-backports (Debian FTP Masters) (signed by: Ben Hutchings)
[2021-10-14] Accepted linux 5.14.12-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2021-10-09] linux 5.14.9-2 MIGRATED to testing (Debian testing watch)
[2021-10-03] Accepted linux 5.14.9-2 (source) into unstable (Salvatore Bonaccorso)
[2021-10-03] Accepted linux 5.14.9-1 (source) into unstable, unstable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)

bugs [bug history graph]

all: 845 890
RC: 2
I&N: 735 772
M&W: 105 113
F&P: 3
patch: 18 20

links

homepage
buildd: logs, exp, checks, clang, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
l10n (-, 41)
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 5.15.0-17.17
7656 bugs (284 patches)