USN-6921-1: Linux kernel vulnerabilities

Published Jul 29, 2024
·
Updated

Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde discovered that an untrusted hypervisor could inject malicious #VC interrupts and compromise the security guarantees of AMD SEV-SNP. This flaw is known as WeSee. A local attacker in control of the hypervisor could use this to expose sensitive information or possibly execute arbitrary code in the trusted execution environment. (CVE-2024-25742) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

Affected Software

59 affected componentsFixes available
Canonical Linux kernel
All of the following
ubuntu/linux-image-6.8.0-1007-gke<6.8.0-1007.10
6.8.0-1007.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1008-raspi<6.8.0-1008.8
6.8.0-1008.8
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1009-ibm<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1009-oem<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1010-nvidia<6.8.0-1010.10
6.8.0-1010.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1010-nvidia-64k<6.8.0-1010.10
6.8.0-1010.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1011-gcp<6.8.0-1011.12
6.8.0-1011.12
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-1012-aws<6.8.0-1012.13
6.8.0-1012.13
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-39-generic<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-6.8.0-39-generic-64k<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-aws<6.8.0-1012.13
6.8.0-1012.13
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-gcp<6.8.0-1011.12
6.8.0-1011.12
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-generic<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-generic-64k<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-generic-64k-hwe-24.04<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-generic-hwe-24.04<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-generic-lpae<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-gke<6.8.0-1007.10
6.8.0-1007.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-ibm<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-ibm-classic<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-ibm-lts-24.04<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-kvm<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-nvidia<6.8.0-1010.10
6.8.0-1010.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-nvidia-64k<6.8.0-1010.10
6.8.0-1010.10
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-oem-24.04<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-oem-24.04a<6.8.0-1009.9
6.8.0-1009.9
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-raspi<6.8.0-1008.8
6.8.0-1008.8
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-virtual<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04
All of the following
ubuntu/linux-image-virtual-hwe-24.04<6.8.0-39.39
6.8.0-39.39
Ubuntu Ubuntu=24.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-6.8.0-1007-gke to a version that resolves this vulnerability.

    Fixed in 6.8.0-1007.10
  2. Upgrade

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

    Fixed in 6.8.0-1008.8
  3. Upgrade

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

    Fixed in 6.8.0-1009.9
  4. Upgrade

    Upgrade ubuntu/linux-image-6.8.0-1009-oem to a version that resolves this vulnerability.

    Fixed in 6.8.0-1009.9
  5. Upgrade

    Upgrade ubuntu/linux-image-6.8.0-1010-nvidia to a version that resolves this vulnerability.

    Fixed in 6.8.0-1010.10
  6. Upgrade

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

    Fixed in 6.8.0-1010.10
  7. Upgrade

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

    Fixed in 6.8.0-1011.12
  8. Upgrade

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

    Fixed in 6.8.0-1012.13
  9. Upgrade

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

    Fixed in 6.8.0-39.39
  10. Upgrade

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

    Fixed in 6.8.0-39.39
  11. Upgrade

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

    Fixed in 6.8.0-1012.13
  12. Upgrade

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

    Fixed in 6.8.0-1011.12
  13. Upgrade

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

    Fixed in 6.8.0-39.39
  14. Upgrade

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

    Fixed in 6.8.0-39.39
  15. Upgrade

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

    Fixed in 6.8.0-39.39
  16. Upgrade

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

    Fixed in 6.8.0-39.39
  17. Upgrade

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

    Fixed in 6.8.0-39.39
  18. Upgrade

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

    Fixed in 6.8.0-1007.10
  19. Upgrade

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

    Fixed in 6.8.0-1009.9
  20. Upgrade

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

    Fixed in 6.8.0-1009.9
  21. Upgrade

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

    Fixed in 6.8.0-1009.9
  22. Upgrade

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

    Fixed in 6.8.0-39.39
  23. Upgrade

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

    Fixed in 6.8.0-1010.10
  24. Upgrade

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

    Fixed in 6.8.0-1010.10
  25. Upgrade

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

    Fixed in 6.8.0-1009.9
  26. Upgrade

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

    Fixed in 6.8.0-1009.9
  27. Upgrade

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

    Fixed in 6.8.0-1008.8
  28. Upgrade

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

    Fixed in 6.8.0-39.39
  29. Upgrade

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

    Fixed in 6.8.0-39.39
  30. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch USN-6921-1

Event History

Jul 29, 2024
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of USN-6921-1?

The severity of USN-6921-1 is classified as high due to the potential for local attackers to exploit the vulnerability.

2

How do I fix USN-6921-1?

To fix USN-6921-1, upgrade to the recommended package version by obtaining the latest linux-image for your Ubuntu 24.04 installation.

3

What does the vulnerability USN-6921-1 affect?

USN-6921-1 affects certain versions of the linux-image package on Ubuntu 24.04 that use AMD SEV-SNP technology.

4

Who discovered the issue reported in USN-6921-1?

The issue reported in USN-6921-1 was discovered by security researchers Benedict Schlüter, Supraja Sridhara, Andrin Bertschi, and Shweta Shinde.

5

Is USN-6921-1 related to specific hardware?

Yes, USN-6921-1 is specifically related to security vulnerabilities in the AMD SEV-SNP hypervisor environment.

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