DEBIAN-CVE-2022-49200

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2022-49200
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2022-49200.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2022-49200
Upstream
Published
2025-02-26T07:00:57Z
Modified
2025-09-19T07:32:38.026614Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: Fix kernel oops in btmtksdiointerrupt Fix the following kernel oops in btmtksdiointerrrupt [ 14.339134] btmtksdiointerrupt+0x28/0x54 [ 14.339139] processsdiopendingirqs+0x68/0x1a0 [ 14.339144] sdioirqwork+0x40/0x70 [ 14.339154] processonework+0x184/0x39c [ 14.339160] workerthread+0x228/0x3e8 [ 14.339168] kthread+0x148/0x3ac [ 14.339176] retfromfork+0x10/0x30 That happened because hdev->poweron is already called before sdiosetdrvdata which btmtksdiointerrupt handler relies on is not properly set up. The details are shown as the below: hciregisterdev would run queuework(hdev->reqworkqueue, &hdev->poweron) as WQHIGHPRI workqueuestruct to complete the power-on sequeunce and thus hcipoweron may run before sdiosetdrvdata is done in btmtksdioprobe. The hcidevdoopen in hcipoweron would initialize the device and enable the interrupt and thus it is possible that btmtksdiointerrupt is being called right before sdiosetdrvdata is filled out. When btmtksdiointerrupt is being called and sdiosetdrvdata is not filled , the kernel oops is going to happen because btmtksdio_interrupt access an uninitialized pointer.

References

Affected packages

Debian:11 / 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
5.10.113-1

Affected versions

5.*

5.10.46-4
5.10.46-5
5.10.70-1~bpo10+1
5.10.70-1
5.10.84-1
5.10.92-1~bpo10+1
5.10.92-1
5.10.92-2
5.10.103-1~bpo10+1
5.10.103-1
5.10.106-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / 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
5.17.3-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

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
5.17.3-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
5.17.3-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}