cve.bz

CVE-2025-21827 linux linux kernel: Improper Locking

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that "the device lock" is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path: Workqueue: hci0 hci_power_on [bluetooth] Call trace: usb_driver_claim_interface btusb_mtk_claim_iso_intf btusb_mtk_setup hci_dev_open_sync hci_power_on process_scheduled_works worker_thread kthread With the above call trace the device lock hasn't been claimed. Claim it. Without this fix, we'd sometimes see the error "Failed to claim iso interface". Sometimes we'd even see worse errors, like a NULL pointer dereference (where `intf->dev.driver` was NULL) with a trace like: Call trace: usb_suspend_both usb_runtime_suspend __rpm_callback rpm_suspend pm_runtime_work process_scheduled_works Both errors appear to be fixed with the proper locking.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-667 Improper Locking
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-21827 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-21827?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-21827?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-21827 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.11 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.13
Linux6.136.13.2
Linuxlater releases6.14

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13, 14linux6.12.13-1DEBIAN-CVE-2025-21827
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-21827
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-21827
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-21827
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-21827
Ubuntu24.04:LTSlinux-gcp-6.11, linux-azure-6.116.11.0-1015.15~24.04.1UBUNTU-CVE-2025-21827 USN-7521-1
Ubuntu24.04:LTSlinux-hwe-6.116.11.0-26.26~24.04.1UBUNTU-CVE-2025-21827 USN-7521-1
Ubuntu24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1014.15~24.04.1UBUNTU-CVE-2025-21827 USN-7521-3
Ubuntu24.04:LTSlinux-nvidia-6.116.11.0-1010.10UBUNTU-CVE-2025-21827
Ubuntu24.04:LTSlinux-oem-6.116.11.0-1022.22UBUNTU-CVE-2025-21827 USN-7521-1
Ubuntu24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-21827
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2025-21827
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-21827

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low-impact flaw was found in the Linux kernel's MediaTek USB Bluetooth (btusb) driver. When a MediaTek Bluetooth USB adapter is powered on, the btusb_mtk_claim_iso_intf() function calls usb_driver_claim_interface() from the hci_power_on workqueue without holding the USB interface device lock that this function requires when it is called from outside the probe path. Because of the missing locking, the ISO interface claim can intermittently fail ("Failed to claim iso interface") or a NULL pointer dereference (intf->dev.driver being NULL) can occur during USB runtime suspend, resulting in a denial of service (system crash) or loss of Bluetooth functionality on systems using affected MediaTek Bluetooth USB hardware. Only availability is affected; the Red Hat severity for this flaw is low, with a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). This differs from the upstream CVE record rating of 7.8, which assumes confidentiality and integrity impacts that the technical evidence for this issue does not support.

Red Hat Enterprise Linux 8 and Red Hat In-Vehicle OS are not affected because the vulnerable code is not present in those releases. Red Hat Enterprise Linux 6 and 7 Extended Lifecycle Support streams are out of support scope. For the affected Red Hat Enterprise Linux 9 and 10 kernel and kernel-rt releases, the fix is deferred because this is a local, availability-only race condition of low severity and limited practical impact, and it will be addressed in a future update. The residual risk of the deferred fix is limited to intermittent Bluetooth interface claim failures or a local denial of service on systems using affected MediaTek Bluetooth USB adapters.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-21827.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON