DEBIAN-CVE-2022-50369

Source
https://security-tracker.debian.org/tracker/CVE-2022-50369
Import Source
https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2022-50369.json
JSON Data
https://api.osv.dev/v1/vulns/DEBIAN-CVE-2022-50369
Upstream
Published
2025-09-17T15:15:35Z
Modified
2025-09-30T05:17:37.065409Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix null-ptr-deref in vkmsrelease() A null-ptr-deref is triggered when it tries to destroy the workqueue in vkms->output.composerworkq in vkmsrelease(). KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f] CPU: 5 PID: 17193 Comm: modprobe Not tainted 6.0.0-11331-gd465bff130bf #24 RIP: 0010:destroyworkqueue+0x2f/0x710 ... Call Trace: <TASK> ? vkmsconfigdebugfsinit+0x50/0x50 [vkms] _devmdrmdevalloc+0x15a/0x1c0 [drm] vkmsinit+0x245/0x1000 [vkms] dooneinitcall+0xd0/0x4f0 doinitmodule+0x1a4/0x680 loadmodule+0x6249/0x7110 _dosysfinitmodule+0x140/0x200 dosyscall64+0x35/0x80 entrySYSCALL64afterhwframe+0x46/0xb0 The reason is that an OOM happened which triggers the destroy of the workqueue, however, the workqueue is alloced in the later process, thus a null-ptr-deref happened. A simple call graph is shown as below: vkmsinit() vkmscreate() devmdrmdevalloc() _devmdrmdevalloc() devmdrmdevinit() devmaddactionorreset() devmaddaction() # an error happened devmdrmdevinitrelease() drmdevput() krefput() drmdevrelease() vkmsrelease() destroyworkqueue() # null-ptr-deref happened vkmsmodesetinit() vkmsoutputinit() vkmscrtcinit() # where the workqueue get allocated Fix this by checking if composerworkq is NULL before passing it to the destroyworkqueue() in vkms_release().

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.178-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
5.10.113-1
5.10.120-1~bpo10+1
5.10.120-1
5.10.127-1
5.10.127-2~bpo10+1
5.10.127-2
5.10.136-1
5.10.140-1
5.10.148-1
5.10.149-1
5.10.149-2
5.10.158-1
5.10.158-2
5.10.162-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
6.1.20-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
6.1.20-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.1.20-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}