How to Fix CVE-2026-31500: Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock in Linux

By Sai Kiran Pandrala

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-23207: Critical Vulnerability in Linux — Critical Vulnerability in Linux
• How to Fix CVE-2026-43085: Security Vulnerability in Linux — Security Vulnerability in Linux
• How to Fix CVE-2026-3234: Improper Neutralization of CRLF Sequences ('CRLF Injection') , Improper Neutralization of CRLF Sequences ('CRLF Injection')
• How to Fix CVE-2026-34001: Red Hat Enterprise Linux 10 (Bundle Sibling) , Red Hat Enterprise Linux 10 (Bundle Sibling)
• How to Fix CVE-2026-43432: Security Vulnerability in Linux , Security Vulnerability in Linux

Last verified: 2026-05-25

CVE-2026-31500 is a bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock in Linux Linux. Fix it by upgrading to 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0.

What is CVE-2026-31500?

CVE-2026-31500 is a bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock flaw in Linux Linux. The vendor has not published a verified CVSS metric at the time of writing. It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock

btintel_hw_error() issues two __hci_cmd_sync() calls (HCI_OP_RESET

and Intel exception-info retrieval) without holding

hci_req_sync_lock(). This lets it race against

hci_dev_do_close() -> btintel_shutdown_combined(), which also runs

__hci_cmd_sync() under the same lock. When both paths manipulate

hdev->req_status/req_rsp concurrently, the close path may free the

response skb first, and the still-running hw_error path hits a

slab-use-after-free in kfree_skb().

Wrap the whole recovery sequence in hci_req_sync_lock/unlock so it

is serialized with every other synchronous HCI command issuer.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31500

Apply the vendor patch. Target the build named in the Fixed in row above (6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky

sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.

# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31500 being exploited in the wild?

As of 2026-05-25, CVE-2026-31500 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31500?

A verified CVSS score is not listed in the public record for CVE-2026-31500. Check the vendor advisory and the NVD page for an updated metric.

What version fixes this?

Upgrade to 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

• Official vendor advisory: https://git.kernel.org/stable/c/5f84e845648dfa86e42de5487f1a774b42f0444d
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31500
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/e10a4cb72468686ffbe8bb2b0520e37f6be1a0c5
• Additional reference: https://git.kernel.org/stable/c/66696648af477dc87859e5e4b607112f5f29d010
• Additional reference: https://git.kernel.org/stable/c/f7d84737663ad4a120d2d8ef1561a4df91282c2e
• Additional reference: https://git.kernel.org/stable/c/94d8e6fe5d0818e9300e514e095a200bd5ff93ae

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*