Skip to content
VulniPulse
High7.3Vendor: MediumRed Hat Linux

High [CVE-2026-63974] Set HCI_CMD_DRAIN_WORKQUEUE during device close

This high-severity Red Hat Linux advisory covers CVE-2026-63974 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat package: kernel-rt.

CVE-2026-63974 Published Jul 19, 2026Updated by vendor Jul 19, 2026
Affected products & platforms
Red Hat LinuxLinux Kernel
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close Since hci_dev_close_sync() can now be called during the reset path, we should also set HCI_CMD_DRAIN_WORKQUEUE. This avoids queuing timeouts while the hdev workqueue is being drained.

When the hci_dev_close_sync() function is called during a device reset, the system may experience queuing timeouts. This occurs because the HCI_CMD_DRAIN_WORKQUEUE flag is not properly set, which can lead to system instability or a denial of service (DoS) condition.

Red Hat severity: Moderate — CVSS 7.3 (CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H). Weakness: CWE-366.

Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 9. Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: kernel-rt.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, disable the Bluetooth service if it is not required. To disable the Bluetooth service: `sudo systemctl stop bluetooth` `sudo systemctl disable bluetooth` Alternatively, prevent the `bluetooth` kernel module from loading by creating a file `/etc/modprobe.d/bluetooth.conf` with the content `blacklist bluetooth`. Then, regenerate the initramfs using `sudo dracut -f -v`. A system reboot is required for the module blacklisting to take effect. Disabling Bluetooth may impact functionality that relies on Bluetooth connectivity.

Official advisory · high-confidence parse· fetched 6 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.