USN-5970-1: Linux kernel vulnerabilities

Published Mar 23, 2023
·
Updated

It was discovered that the KVM VMX implementation in the Linux kernel did not properly handle indirect branch prediction isolation between L1 and L2 VMs. An attacker in a guest VM could use this to expose sensitive information from the host OS or other guest VMs. (CVE-2022-2196) It was discovered that a race condition existed in the Xen network backend driver in the Linux kernel when handling dropped packets in certain circumstances. An attacker could use this to cause a denial of service (kernel deadlock). (CVE-2022-42328, CVE-2022-42329) Gerald Lee discovered that the USB Gadget file system implementation in the Linux kernel contained a race condition, leading to a use-after-free vulnerability in some situations. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2022-4382) José Oliveira and Rodrigo Branco discovered that the prctl syscall implementation in the Linux kernel did not properly protect against indirect branch prediction attacks in some situations. A local attacker could possibly use this to expose sensitive information. (CVE-2023-0045) It was discovered that a use-after-free vulnerability existed in the Advanced Linux Sound Architecture (ALSA) subsystem. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-0266) It was discovered that the iouring subsystem in the Linux kernel contained 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-2023-0469) It was discovered that the CIFS network file system implementation in the Linux kernel contained a user-after-free vulnerability. A local attacker could possibly use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2023-1195) It was discovered that the RNDIS USB driver in the Linux kernel contained an integer overflow vulnerability. A local attacker with physical access could plug in a malicious USB device to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-23559)

Affected Software

55 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-5.19.0-38-generic-lpae<5.19.0-38.39
5.19.0-38.39
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-virtual<5.19.0.38.34
5.19.0.38.34
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1015-raspi<5.19.0-1015.22
5.19.0-1015.22
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-generic-64k<5.19.0.38.34
5.19.0.38.34
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-38-generic-64k<5.19.0-38.39
5.19.0-38.39
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-aws<5.19.0.1022.19
5.19.0.1022.19
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-gcp<5.19.0.1019.16
5.19.0.1019.16
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-ibm<5.19.0.1019.16
5.19.0.1019.16
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1019-ibm<5.19.0-1019.21
5.19.0-1019.21
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1021-lowlatency<5.19.0-1021.22
5.19.0-1021.22
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1021-lowlatency-64k<5.19.0-1021.22
5.19.0-1021.22
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1022-aws<5.19.0-1022.23
5.19.0-1022.23
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-azure<5.19.0.1022.18
5.19.0.1022.18
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-raspi-nolpae<5.19.0.1015.14
5.19.0.1015.14
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1015-raspi-nolpae<5.19.0-1015.22
5.19.0-1015.22
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1019-gcp<5.19.0-1019.21
5.19.0-1019.21
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1020-kvm<5.19.0-1020.21
5.19.0-1020.21
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-lowlatency-64k<5.19.0.1021.17
5.19.0.1021.17
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-oracle<5.19.0.1019.16
5.19.0.1019.16
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-generic<5.19.0.38.34
5.19.0.38.34
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-raspi<5.19.0.1015.14
5.19.0.1015.14
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1022-azure<5.19.0-1022.23
5.19.0-1022.23
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-kvm<5.19.0.1020.17
5.19.0.1020.17
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-38-generic<5.19.0-38.39
5.19.0-38.39
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-generic-lpae<5.19.0.38.34
5.19.0.38.34
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-5.19.0-1019-oracle<5.19.0-1019.22
5.19.0-1019.22
Ubuntu Ubuntu=22.10
All of the following
ubuntu/linux-image-lowlatency<5.19.0.1021.17
5.19.0.1021.17
Ubuntu Ubuntu=22.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-38-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.19.0-38.39
  2. Upgrade

    Upgrade ubuntu/linux-image-virtual to a version that resolves this vulnerability.

    Fixed in 5.19.0.38.34
  3. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1015-raspi to a version that resolves this vulnerability.

    Fixed in 5.19.0-1015.22
  4. Upgrade

    Upgrade ubuntu/linux-image-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.19.0.38.34
  5. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-38-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.19.0-38.39
  6. Upgrade

    Upgrade ubuntu/linux-image-aws to a version that resolves this vulnerability.

    Fixed in 5.19.0.1022.19
  7. Upgrade

    Upgrade ubuntu/linux-image-gcp to a version that resolves this vulnerability.

    Fixed in 5.19.0.1019.16
  8. Upgrade

    Upgrade ubuntu/linux-image-ibm to a version that resolves this vulnerability.

    Fixed in 5.19.0.1019.16
  9. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1019-ibm to a version that resolves this vulnerability.

    Fixed in 5.19.0-1019.21
  10. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1021-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.19.0-1021.22
  11. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1021-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 5.19.0-1021.22
  12. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1022-aws to a version that resolves this vulnerability.

    Fixed in 5.19.0-1022.23
  13. Upgrade

    Upgrade ubuntu/linux-image-azure to a version that resolves this vulnerability.

    Fixed in 5.19.0.1022.18
  14. Upgrade

    Upgrade ubuntu/linux-image-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 5.19.0.1015.14
  15. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1015-raspi-nolpae to a version that resolves this vulnerability.

    Fixed in 5.19.0-1015.22
  16. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1019-gcp to a version that resolves this vulnerability.

    Fixed in 5.19.0-1019.21
  17. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1020-kvm to a version that resolves this vulnerability.

    Fixed in 5.19.0-1020.21
  18. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 5.19.0.1021.17
  19. Upgrade

    Upgrade ubuntu/linux-image-oracle to a version that resolves this vulnerability.

    Fixed in 5.19.0.1019.16
  20. Upgrade

    Upgrade ubuntu/linux-image-generic to a version that resolves this vulnerability.

    Fixed in 5.19.0.38.34
  21. Upgrade

    Upgrade ubuntu/linux-image-raspi to a version that resolves this vulnerability.

    Fixed in 5.19.0.1015.14
  22. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1022-azure to a version that resolves this vulnerability.

    Fixed in 5.19.0-1022.23
  23. Upgrade

    Upgrade ubuntu/linux-image-kvm to a version that resolves this vulnerability.

    Fixed in 5.19.0.1020.17
  24. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-38-generic to a version that resolves this vulnerability.

    Fixed in 5.19.0-38.39
  25. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.19.0.38.34
  26. Upgrade

    Upgrade ubuntu/linux-image-5.19.0-1019-oracle to a version that resolves this vulnerability.

    Fixed in 5.19.0-1019.22
  27. Upgrade

    Upgrade ubuntu/linux-image-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.19.0.1021.17

Event History

Mar 23, 2023
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the vulnerability ID for this Linux kernel vulnerability?

The vulnerability ID for this Linux kernel vulnerability is CVE-2022-2196.

2

What is the impact of CVE-2022-2196?

CVE-2022-2196 can allow an attacker in a guest virtual machine to expose sensitive information from the host OS or other guest VMs.

3

Which versions of Linux kernel are affected by CVE-2022-2196?

Linux kernel versions 5.19.0-38.39 and earlier are affected by CVE-2022-2196.

4

What is the recommended remedy for CVE-2022-2196?

The recommended remedy for CVE-2022-2196 is to update to version 5.19.0-38.39 or later of the Linux kernel.

5

Where can I find more information about CVE-2022-2196?

More information about CVE-2022-2196 can be found at the following link: [CVE-2022-2196](https://ubuntu.com/security/CVE-2022-2196)

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203