DEBIAN-CVE-2025-21827

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2025-21827
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2025-21827.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2025-21827
Upstream
Published
2025-03-06T16:15:54Z
Modified
2025-09-19T06:23:43Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usbdriverclaiminterface() The documentation for usbdriverclaiminterface() 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 hcipoweron [bluetooth] Call trace: usbdriverclaiminterface btusbmtkclaimisointf btusbmtksetup hcidevopensync hcipoweron processscheduledworks workerthread 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: usbsuspendboth usbruntimesuspend _rpmcallback rpmsuspend pmruntimework processscheduledworks Both errors appear to be fixed with the proper locking.

References

Affected packages

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.12.13-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:14 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
6.12.13-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}