USN-4369-1: Linux kernel vulnerabilities
It was discovered that the btrfs implementation in the Linux kernel did not properly detect that a block was marked dirty in some situations. An attacker could use this to specially craft a file system image that, when unmounted, could cause a denial of service (system crash). (CVE-2019-19377) Tristan Madani discovered that the file locking implementation in the Linux kernel contained a race condition. A local attacker could possibly use this to cause a denial of service or expose sensitive information. (CVE-2019-19769) It was discovered that the Serial CAN interface driver in the Linux kernel did not properly initialize data. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2020-11494) It was discovered that the linux kernel did not properly validate certain mount options to the tmpfs virtual memory file system. A local attacker with the ability to specify mount options could use this to cause a denial of service (system crash). (CVE-2020-11565) It was discovered that the OV51x USB Camera device driver in the Linux kernel did not properly validate device metadata. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2020-11608) It was discovered that the STV06XX USB Camera device driver in the Linux kernel did not properly validate device metadata. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2020-11609) It was discovered that the Xirlink C-It USB Camera device driver in the Linux kernel did not properly validate device metadata. A physically proximate attacker could use this to cause a denial of service (system crash). (CVE-2020-11668) It was discovered that the block layer in the Linux kernel contained a race condition leading to a use-after-free vulnerability. A local attacker could possibly use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2020-12657)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1017-kvmto a version that resolves this vulnerability.Fixed in 5.3.0-1017.19 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1018-oracleto a version that resolves this vulnerability.Fixed in 5.3.0-1018.20 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1019-awsto a version that resolves this vulnerability.Fixed in 5.3.0-1019.21 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1020-gcpto a version that resolves this vulnerability.Fixed in 5.3.0-1020.22 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1022-azureto a version that resolves this vulnerability.Fixed in 5.3.0-1022.23 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1025-raspi2to a version that resolves this vulnerability.Fixed in 5.3.0-1025.27 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-genericto a version that resolves this vulnerability.Fixed in 5.3.0-53.47 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.3.0-53.47 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-lowlatencyto a version that resolves this vulnerability.Fixed in 5.3.0-53.47 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-snapdragonto a version that resolves this vulnerability.Fixed in 5.3.0-53.47 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 5.3.0.1019.31 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 5.3.0.1022.41 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 5.3.0.1020.31 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 5.3.0.53.45 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.3.0.53.45 - Upgrade
Upgrade
ubuntu/linux-image-gketo a version that resolves this vulnerability.Fixed in 5.3.0.1020.31 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 5.3.0.1017.19 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 5.3.0.53.45 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 5.3.0.1018.33 - Upgrade
Upgrade
ubuntu/linux-image-raspi2to a version that resolves this vulnerability.Fixed in 5.3.0.1025.22 - Upgrade
Upgrade
ubuntu/linux-image-snapdragonto a version that resolves this vulnerability.Fixed in 5.3.0.53.45 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 5.3.0.53.45 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1018-oracleto a version that resolves this vulnerability.Fixed in 5.3.0-1018.20~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1019-awsto a version that resolves this vulnerability.Fixed in 5.3.0-1019.21~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1020-gcpto a version that resolves this vulnerability.Fixed in 5.3.0-1020.22~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1020-gketo a version that resolves this vulnerability.Fixed in 5.3.0-1020.22~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-1022-azureto a version that resolves this vulnerability.Fixed in 5.3.0-1022.23~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-genericto a version that resolves this vulnerability.Fixed in 5.3.0-53.47~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-generic-lpaeto a version that resolves this vulnerability.Fixed in 5.3.0-53.47~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-5.3.0-53-lowlatencyto a version that resolves this vulnerability.Fixed in 5.3.0-53.47~18.04.1 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 5.3.0.1019.20 - Upgrade
Upgrade
ubuntu/linux-image-aws-edgeto a version that resolves this vulnerability.Fixed in 5.3.0.1019.20 - Upgrade
Upgrade
ubuntu/linux-image-azureto a version that resolves this vulnerability.Fixed in 5.3.0.1022.22 - Upgrade
Upgrade
ubuntu/linux-image-azure-edgeto a version that resolves this vulnerability.Fixed in 5.3.0.1022.22 - Upgrade
Upgrade
ubuntu/linux-image-gcpto a version that resolves this vulnerability.Fixed in 5.3.0.1020.19 - Upgrade
Upgrade
ubuntu/linux-image-gcp-edgeto a version that resolves this vulnerability.Fixed in 5.3.0.1020.19 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.3.0.53.109 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpae-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.3.0.53.109 - Upgrade
Upgrade
ubuntu/linux-image-gke-5.3to a version that resolves this vulnerability.Fixed in 5.3.0.1020.10 - Upgrade
Upgrade
ubuntu/linux-image-gkeop-5.3to a version that resolves this vulnerability.Fixed in 5.3.0.53.109 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.3.0.53.109 - Upgrade
Upgrade
ubuntu/linux-image-oracleto a version that resolves this vulnerability.Fixed in 5.3.0.1018.19 - Upgrade
Upgrade
ubuntu/linux-image-snapdragon-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.3.0.53.109 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-18.04to a version that resolves this vulnerability.Fixed in 5.3.0.53.109
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-4369-1?
USN-4369-1 is classified as a high-severity vulnerability due to the potential for denial of service.
How do I fix USN-4369-1?
To resolve USN-4369-1, you should upgrade to the recommended patched versions of the affected Linux kernel packages.
Which Ubuntu versions are affected by USN-4369-1?
USN-4369-1 affects Ubuntu 19.10 and versions around it.
What does the vulnerability USN-4369-1 affect specifically?
USN-4369-1 affects the btrfs implementation in the Linux kernel regarding its handling of dirty block detection.
Can the exploitation of USN-4369-1 lead to any serious consequences?
Yes, exploitation of USN-4369-1 can lead to a denial of service resulting in a system crash.