USN-5466-1
Vulnerability Summary
Timeline
Description
linux, linux-aws, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-gcp, linux-gcp-4.15, linux-hwe, linux-kvm, linux-oracle, linux-raspi2, linux-snapdragon vulnerabilities It was discovered that the Linux kernel did not properly restrict access to the kernel debugger when booted in secure boot environments. A privileged attacker could use this to bypass UEFI Secure Boot restrictions. (CVE-2022-21499) Aaron Adams discovered that the netfilter subsystem in the Linux kernel did not properly handle the removal of stateful expressions in some situations, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2022-1966) It was discovered that the SCTP protocol implementation in the Linux kernel did not properly verify VTAGs in some situations. A remote attacker could possibly use this to cause a denial of service (connection disassociation). (CVE-2021-3772) It was discovered that the btrfs file system implementation in the Linux kernel did not properly handle locking in certain error conditions. A local attacker could use this to cause a denial of service (kernel deadlock). (CVE-2021-4149) David Bouman discovered that the netfilter subsystem in the Linux kernel did not initialize memory in some situations. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2022-1016) It was discovered that the virtual graphics memory manager implementation in the Linux kernel was subject to a race condition, potentially leading to an information leak. (CVE-2022-1419) 赵子轩 discovered that the 802.2 LLC type 2 driver in the Linux kernel did not properly perform reference counting in some error conditions. A local attacker could use this to cause a denial of service. (CVE-2022-28356) It was discovered that the EMS CAN/USB interface implementation in the Linux kernel contained a double-free vulnerability when handling certain error conditions. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2022-28390)
Affected Systems
- ubuntu•linux
< 4.15.0-184.194
- ubuntu•linux-aws
< 4.15.0-1133.143
- ubuntu•linux-aws-hwe
< 4.15.0-1133.143~16.04.1
- ubuntu•linux-azure
< 4.15.0-1142.156~14.04.1 | < 4.15.0-1142.156~16.04.1
- ubuntu•linux-azure-4.15
< 4.15.0-1142.156
- ubuntu•linux-gcp
< 4.15.0-1127.142~16.04.1
- ubuntu•linux-gcp-4.15
< 4.15.0-1127.142
- ubuntu•linux-hwe
< 4.15.0-184.194~16.04.1
- ubuntu•linux-kvm
< 4.15.0-1119.123
- ubuntu•linux-oracle
< 4.15.0-1098.108~16.04.1 | < 4.15.0-1098.108
- ubuntu•linux-raspi2
< 4.15.0-1114.122
- ubuntu•linux-snapdragon
< 4.15.0-1132.142
References (9)
- https://ubuntu.com/security/notices/USN-5466-1
- https://ubuntu.com/security/CVE-2021-3772
- https://ubuntu.com/security/CVE-2021-4149
- https://ubuntu.com/security/CVE-2022-1016
- https://ubuntu.com/security/CVE-2022-1419
- https://ubuntu.com/security/CVE-2022-1966
- https://ubuntu.com/security/CVE-2022-21499
- https://ubuntu.com/security/CVE-2022-28356
- https://ubuntu.com/security/CVE-2022-28390