UBUNTU-CVE-2025-38047: Medium severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are exposed to this issue?

The issue affects systems using a listed Ubuntu kernel package where FRED is enabled and the system resumes from S4 hibernation. The affected package list includes linux-riscv, linux-hwe-edge, linux-azure-fde, linux-realtime, linux-aws-5.0, linux-aws-5.3, linux-azure, and linux-azure-5.3.

Q: What must occur for the failure to be triggered?

A system must wake from S4 hibernation. During resume, the restore kernel can leave FRED MSRs configured for itself rather than for the hibernated image kernel, causing the resumed system to hang.

Q: Does exploitation require remote access or user interaction?

No. The supplied vector indicates local access, low attack complexity, low privileges, and no user interaction. The described impact is denial of service through a system hang during S4 resume.

Q: How can administrators identify potentially affected systems?

Identify hosts running one of the listed Ubuntu kernel packages, with FRED enabled, that use S4 hibernation. A hang while resuming from hibernation is consistent with the described condition.

Published Jun 18, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: x86/fred: Fix system hang during S4 resume with FRED enabled Upon a wakeup from S4, the restore kernel starts and initializes the FRED MSRs as needed from its perspective. It then loads a hibernation image, including the image kernel, and attempts to load image pages directly into their original page frames used before hibernation unless those frames are currently in use. Once all pages are moved to their original locations, it jumps to a "trampoline" page in the image kernel. At this point, the image kernel takes control, but the FRED MSRs still contain values set by the restore kernel, which may differ from those set by the image kernel before hibernation. Therefore, the image kernel must ensure the FRED MSRs have the same values as before hibernation. Since these values depend only on the location of the kernel text and data, they can be recomputed from scratch.

Affected Software

98 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-aws-6.14<6.14.0-1013.13~24.04.1

6.14.0-1013.13~24.04.1

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-fde-6.17*

ubuntu/linux-azure-nvidia-6.14<6.14.0-1007.7

6.14.0-1007.7

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14<6.14.0-1016.17~24.04.1

6.14.0-1016.17~24.04.1

ubuntu/linux-hwe-6.11*

ubuntu/linux-intel*

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia-6.11*

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14<6.14.0-1012.12

6.14.0-1012.12

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle-6.14<6.14.0-1013.13~24.04.1

6.14.0-1013.13~24.04.1

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14<6.14.0-32.32.1~24.04.1

6.14.0-32.32.1~24.04.1

ubuntu/linux-realtime-6.14<6.14.0-1012.12~24.04.1

6.14.0-1012.12~24.04.1

ubuntu/linux-azure-fde*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1013.13~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-nvidia-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1007.7
Upgrade
Upgrade ubuntu/linux-gcp-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1016.17~24.04.1
Upgrade
Upgrade ubuntu/linux-oem-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1012.12
Upgrade
Upgrade ubuntu/linux-oracle-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1013.13~24.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-32.32.1~24.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.14 to a version that resolves this vulnerability.
Fixed in 6.14.0-1012.12~24.04.1
Configuration
Ensure the image kernel recomputes and restores the FRED MSRs so they match the values from before hibernation.
Linux kernel FRED FRED MSRs = same values as before hibernation

Event History

Jun 18, 2025

CVE Published

via OSV·10:15 AM

Data Sourced

via OSV·10:15 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are exposed to this issue?

The issue affects systems using a listed Ubuntu kernel package where FRED is enabled and the system resumes from S4 hibernation. The affected package list includes linux-riscv, linux-hwe-edge, linux-azure-fde, linux-realtime, linux-aws-5.0, linux-aws-5.3, linux-azure, and linux-azure-5.3.

What must occur for the failure to be triggered?

A system must wake from S4 hibernation. During resume, the restore kernel can leave FRED MSRs configured for itself rather than for the hibernated image kernel, causing the resumed system to hang.

Does exploitation require remote access or user interaction?

No. The supplied vector indicates local access, low attack complexity, low privileges, and no user interaction. The described impact is denial of service through a system hang during S4 resume.

How can administrators identify potentially affected systems?

Identify hosts running one of the listed Ubuntu kernel packages, with FRED enabled, that use S4 hibernation. A hang while resuming from hibernation is consistent with the described condition.

UBUNTU-CVE-2025-38047: Medium severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are exposed to this issue?

What must occur for the failure to be triggered?

Does exploitation require remote access or user interaction?

How can administrators identify potentially affected systems?

Company

Resources

Contact

Frequently Asked Questions

Which systems are exposed to this issue?

What must occur for the failure to be triggered?

Does exploitation require remote access or user interaction?

How can administrators identify potentially affected systems?