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

Q: Who can exploit this issue?

An attacker needs local access with low privileges. The affected system must use a Bluetooth controller for which READ_VOICE_SETTING is unsupported or behaves incorrectly.

Q: What capability is needed to trigger the controller failure?

The issue is associated with establishing an SCO Bluetooth connection without the required voice_setting. A successful trigger can cause the Bluetooth controller to lock up, affecting availability.

Q: What can be done before an update is available?

Avoid SCO Bluetooth use on systems with controllers that do not properly support READ_VOICE_SETTING. The kernel fix disables SCO support when that command is unsupported or broken, preventing the unsafe connection setup.

Published Jul 3, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Disable SCO support if READVOICESETTING is unsupported/broken A SCO connection without the proper voicesetting can cause the controller to lock up.

Affected Software

97 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-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
Disable SCO support when READ_VOICE_SETTING is unsupported or broken to prevent controller lockups.
Linux kernel Bluetooth SCO support = disabled

Event History

Jul 3, 2025

CVE Published

via OSV·09:15 AM

Data Sourced

via OSV·09:15 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

Who can exploit this issue?

An attacker needs local access with low privileges. The affected system must use a Bluetooth controller for which READ_VOICE_SETTING is unsupported or behaves incorrectly.

What capability is needed to trigger the controller failure?

The issue is associated with establishing an SCO Bluetooth connection without the required voice_setting. A successful trigger can cause the Bluetooth controller to lock up, affecting availability.

What can be done before an update is available?

Avoid SCO Bluetooth use on systems with controllers that do not properly support READ_VOICE_SETTING. The kernel fix disables SCO support when that command is unsupported or broken, preventing the unsafe connection setup.

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

Affected Software

Remediation

Event History

Frequently Asked Questions

Who can exploit this issue?

What capability is needed to trigger the controller failure?

What can be done before an update is available?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What capability is needed to trigger the controller failure?

What can be done before an update is available?