USN-6502-1: Linux kernel vulnerabilities
Ivan D Barrera, Christopher Bednarz, Mustafa Ismail, and Shiraz Saleem discovered that the InfiniBand RDMA driver in the Linux kernel did not properly check for zero-length STAG or MR registration. A remote attacker could possibly use this to execute arbitrary code. (CVE-2023-25775) Yu Hao discovered that the UBI driver in the Linux kernel did not properly check for MTD with zero erasesize during device attachment. A local privileged attacker could use this to cause a denial of service (system crash). (CVE-2023-31085) Manfred Rudigier discovered that the Intel(R) PCI-Express Gigabit (igb) Ethernet driver in the Linux kernel did not properly validate received frames that are larger than the set MTU size, leading to a buffer overflow vulnerability. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-45871) Maxim Levitsky discovered that the KVM nested virtualization (SVM) implementation for AMD processors in the Linux kernel did not properly handle x2AVIC MSRs. An attacker in a guest VM could use this to cause a denial of service (host kernel crash). (CVE-2023-5090) It was discovered that the SMB network file sharing protocol implementation in the Linux kernel did not properly handle certain error conditions, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-5345)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1009-starfiveto a version that resolves this vulnerability.Fixed in 6.2.0-1009.10 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1016-awsto a version that resolves this vulnerability.Fixed in 6.2.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-kvmto a version that resolves this vulnerability.Fixed in 6.2.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-raspito a version that resolves this vulnerability.Fixed in 6.2.0-1017.19 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-genericto a version that resolves this vulnerability.Fixed in 6.2.0-37.38 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0-37.38 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0-37.38 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 6.2.0.1016.17 - Upgrade
Upgrade
ubuntu/linux-image-genericto a version that resolves this vulnerability.Fixed in 6.2.0.37.37 - Upgrade
Upgrade
ubuntu/linux-image-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0.37.37 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0.37.37 - Upgrade
Upgrade
ubuntu/linux-image-kvmto a version that resolves this vulnerability.Fixed in 6.2.0.1017.17 - Upgrade
Upgrade
ubuntu/linux-image-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0.1017.17 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0.1017.17 - Upgrade
Upgrade
ubuntu/linux-image-raspito a version that resolves this vulnerability.Fixed in 6.2.0.1017.20 - Upgrade
Upgrade
ubuntu/linux-image-raspi-nolpaeto a version that resolves this vulnerability.Fixed in 6.2.0.1017.20 - Upgrade
Upgrade
ubuntu/linux-image-starfiveto a version that resolves this vulnerability.Fixed in 6.2.0.1009.12 - Upgrade
Upgrade
ubuntu/linux-image-virtualto a version that resolves this vulnerability.Fixed in 6.2.0.37.37 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1016-awsto a version that resolves this vulnerability.Fixed in 6.2.0-1016.16~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-lowlatencyto a version that resolves this vulnerability.Fixed in 6.2.0-1017.17~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-1017-lowlatency-64kto a version that resolves this vulnerability.Fixed in 6.2.0-1017.17~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-genericto a version that resolves this vulnerability.Fixed in 6.2.0-37.38~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-generic-64kto a version that resolves this vulnerability.Fixed in 6.2.0-37.38~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-6.2.0-37-generic-lpaeto a version that resolves this vulnerability.Fixed in 6.2.0-37.38~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-awsto a version that resolves this vulnerability.Fixed in 6.2.0.1016.16~22.04.1 - Upgrade
Upgrade
ubuntu/linux-image-generic-64k-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.37.38~22.04.15 - Upgrade
Upgrade
ubuntu/linux-image-generic-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.37.38~22.04.15 - Upgrade
Upgrade
ubuntu/linux-image-generic-lpae-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.37.38~22.04.15 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-64k-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.1017.17~22.04.14 - Upgrade
Upgrade
ubuntu/linux-image-lowlatency-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.1017.17~22.04.14 - Upgrade
Upgrade
ubuntu/linux-image-virtual-hwe-22.04to a version that resolves this vulnerability.Fixed in 6.2.0.37.38~22.04.15
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-6502-1?
USN-6502-1 is classified as a high severity vulnerability due to its potential for remote code execution.
How do I fix USN-6502-1?
To fix USN-6502-1, upgrade your Linux kernel to the specified versions, including linux-image-6.2.0-1009.10 or later for Ubuntu 23.04.
Which Ubuntu versions are affected by USN-6502-1?
USN-6502-1 affects Ubuntu 22.04 and 23.04 systems running the vulnerable Linux kernel versions.
What is the impact of exploiting USN-6502-1?
Exploiting USN-6502-1 could allow a remote attacker to execute arbitrary code on the affected system.
Is there a workaround for USN-6502-1?
There are no effective workarounds for USN-6502-1, so upgrading to a fixed version is necessary.