CVE-2022-50282
published 2025-09-15CVE-2022-50282: In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
chardev: fix error handling in cdev_device_add()
While doing fault injection test, I got the following report:
------------[ cut here ]------------
kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called.
WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0
CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
RIP: 0010:kobject_put+0x23d/0x4e0
Call Trace:
cdev_device_add+0x15e/0x1b0
__iio_device_register+0x13b4/0x1af0 [industrialio]
__devm_iio_device_register+0x22/0x90 [industrialio]
max517_probe+0x3d8/0x6b4 [max517]
i2c_device_probe+0xa81/0xc00
When device_add() is injected fault and returns error, if dev->devt is not set,
cdev_add() is not called, cdev_del() is not needed. Fix this by checking dev->devt
in error path.
Affected
30 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < 6acf8597c5b04f455ee0649e11e5f3bcd28f381e | 6acf8597c5b04f455ee0649e11e5f3bcd28f381e |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < 34d17b39bceef25e4cf9805cd59250ae05d0a139 | 34d17b39bceef25e4cf9805cd59250ae05d0a139 |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < d85b5247a79355b8432bfd9ac871f96117f750d4 | d85b5247a79355b8432bfd9ac871f96117f750d4 |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < c46db6088bccff5115674d583fef46ede80077a2 | c46db6088bccff5115674d583fef46ede80077a2 |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < 28dc61cc49c6e995121c6d86bef4b73df78dda80 | 28dc61cc49c6e995121c6d86bef4b73df78dda80 |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < b5de1eac71fec1af7723f1083d23a24789fd795c | b5de1eac71fec1af7723f1083d23a24789fd795c |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < 85a5660491b507d33662b8e81c142e6041e642eb | 85a5660491b507d33662b8e81c142e6041e642eb |
| linux | linux | >= 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 < 11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797 | 11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797 |
| linux | linux | >= 3.16.83 < 3.17 | 3.17 |
| linux | linux | >= 4.4.224 < 4.5 | 4.5 |
| linux | linux | >= 4.9.224 < 4.9.337 | 4.9.337 |
| linux | linux | >= da97a80a657d1b1b50ef633e8ff5dbf0d417fc8d < 5d2146889fad4cb9e6c13e790d4cfd871486eca8 | 5d2146889fad4cb9e6c13e790d4cfd871486eca8 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 3.16.83 < 3.17 | 3.17 |
| linux | linux_kernel | >= 4.12 < 4.14.303 | 4.14.303 |
| linux | linux_kernel | >= 4.15 < 4.19.270 | 4.19.270 |
| linux | linux_kernel | >= 4.20 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 4.4.224 < 4.5 | 4.5 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-50282: In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test,
osv·2025-09-15·CVSS 5.5
CVE-2022-50282 [MEDIUM] CVE-2022-50282: In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test,
In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got the following report: ------------[ cut here ]------------ kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called. WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0 CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:kobject_put+0x23d/0x4e0 Call Trace: cdev_device_add+0x15e/0x1b0 __iio_device_register+0x13b4/0x1af0 [industrialio] __devm_iio_device_register+0x22/0x90 [industrialio] max517_probe+0x3d8/0x6b4 [max517] i2c_device_probe+0xa81/0xc00 When device_add() is injected fau
GHSA
GHSA-3mx8-688w-x5vh: In the Linux kernel, the following vulnerability has been resolved:
chardev: fix error handling in cdev_device_add()
While doing fault injection tes
ghsa_unreviewed·2025-09-15
CVE-2022-50282 [MEDIUM] CWE-908 GHSA-3mx8-688w-x5vh: In the Linux kernel, the following vulnerability has been resolved:
chardev: fix error handling in cdev_device_add()
While doing fault injection tes
In the Linux kernel, the following vulnerability has been resolved:
chardev: fix error handling in cdev_device_add()
While doing fault injection test, I got the following report:
------------[ cut here ]------------
kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called.
WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0
CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
RIP: 0010:kobject_put+0x23d/0x4e0
Call Trace:
cdev_device_add+0x15e/0x1b0
__iio_device_register+0x13b4/0x1af0 [industrialio]
__devm_iio_device_register+0x22/0x90 [industrialio]
max517_probe+0x3d8/0x6b4 [max517]
i2c_device_probe+0xa81/0xc00
When device_add() is injecte
Red Hat
kernel: chardev: fix error handling in cdev_device_add()
vendor_redhat·2025-09-15·CVSS 5.5
CVE-2022-50282 [MEDIUM] CWE-908 kernel: chardev: fix error handling in cdev_device_add()
kernel: chardev: fix error handling in cdev_device_add()
In the Linux kernel, the following vulnerability has been resolved:
chardev: fix error handling in cdev_device_add()
While doing fault injection test, I got the following report:
------------[ cut here ]------------
kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called.
WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0
CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
RIP: 0010:kobject_put+0x23d/0x4e0
Call Trace:
cdev_device_add+0x15e/0x1b0
__iio_device_register+0x13b4/0x1af0 [industrialio]
__devm_iio_device_register+0x22/0x90 [industrialio]
max517_probe+0x3d8/0x6b4 [max517]
i2c
Debian
CVE-2022-50282: linux - In the Linux kernel, the following vulnerability has been resolved: chardev: fi...
vendor_debian·2022·CVSS 5.5
CVE-2022-50282 [MEDIUM] CVE-2022-50282: linux - In the Linux kernel, the following vulnerability has been resolved: chardev: fi...
In the Linux kernel, the following vulnerability has been resolved: chardev: fix error handling in cdev_device_add() While doing fault injection test, I got the following report: ------------[ cut here ]------------ kobject: '(null)' (0000000039956980): is not initialized, yet kobject_put() is being called. WARNING: CPU: 3 PID: 6306 at kobject_put+0x23d/0x4e0 CPU: 3 PID: 6306 Comm: 283 Tainted: G W 6.1.0-rc2-00005-g307c1086d7c9 #1253 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:kobject_put+0x23d/0x4e0 Call Trace: cdev_device_add+0x15e/0x1b0 __iio_device_register+0x13b4/0x1af0 [industrialio] __devm_iio_device_register+0x22/0x90 [industrialio] max517_probe+0x3d8/0x6b4 [max517] i2c_device_probe+0xa81/0xc00 When device_add() is injected fau
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797https://git.kernel.org/stable/c/28dc61cc49c6e995121c6d86bef4b73df78dda80https://git.kernel.org/stable/c/34d17b39bceef25e4cf9805cd59250ae05d0a139https://git.kernel.org/stable/c/5d2146889fad4cb9e6c13e790d4cfd871486eca8https://git.kernel.org/stable/c/6acf8597c5b04f455ee0649e11e5f3bcd28f381ehttps://git.kernel.org/stable/c/85a5660491b507d33662b8e81c142e6041e642ebhttps://git.kernel.org/stable/c/b5de1eac71fec1af7723f1083d23a24789fd795chttps://git.kernel.org/stable/c/c46db6088bccff5115674d583fef46ede80077a2https://git.kernel.org/stable/c/d85b5247a79355b8432bfd9ac871f96117f750d4
2025-09-15
Published