DEBIAN-CVE-2022-50468

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2022-50468
Import Source
https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2022-50468.json
JSON Data
https://api.osv.dev/v1/vulns/DEBIAN-CVE-2022-50468
Upstream
Published
2025-10-01T12:15:40Z
Modified
2025-10-02T09:25:34.587460Z
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: crosusbpdnotify: Fix error handling in crosusbpdnotifyinit() The following WARNING message was given when rmmod crosusbpdnotify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270 driverunregister+0x8a/0xb0 Modules linked in: crosusbpdnotify(-) CPU: 0 PID: 253 Comm: rmmod Not tainted 6.1.0-rc3 #24 ... Call Trace: <TASK> crosusbpdnotifyexit+0x11/0x1e [crosusbpdnotify] _x64sysdeletemodule+0x3c7/0x570 ? _ia32sysdeletemodule+0x570/0x570 ? lockisheldtype+0xe3/0x140 ? syscallenterfromusermode+0x17/0x50 ? rcureadlockschedheld+0xa0/0xd0 ? syscallenterfromusermode+0x1c/0x50 dosyscall64+0x37/0x90 entrySYSCALL64afterhwframe+0x63/0xcd RIP: 0033:0x7f333fe9b1b7 The reason is that the crosusbpdnotifyinit() does not check the return value of platformdriverregister(), and the crosusbpdnotify can install successfully even if platformdriverregister() failed. Fix by checking the return value of platformdriverregister() and unregister crosusbpdnotifyplat_driver when it failed.

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.4-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.4-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.4-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}