Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50282

chardev: fix error handling in cdev_device_add()

Medium5.5EPSS 0.18%
Published
Updated
Reserved
Assigned by
Linux

Description

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: <TASK> 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.

Scores

CVSS scores of CVE-2022-50282, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected da97a80a657d1b1b50ef633e8ff5dbf0d417fc8d – < 5d2146889fad4cb9e6c13e790d4cfd871486eca8
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < 6acf8597c5b04f455ee0649e11e5f3bcd28f381e
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < 34d17b39bceef25e4cf9805cd59250ae05d0a139
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < d85b5247a79355b8432bfd9ac871f96117f750d4
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < c46db6088bccff5115674d583fef46ede80077a2
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < 28dc61cc49c6e995121c6d86bef4b73df78dda80
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < b5de1eac71fec1af7723f1083d23a24789fd795c
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < 85a5660491b507d33662b8e81c142e6041e642eb
    • affected 233ed09d7fdacf592ee91e6c97ce5f4364fbe7c0 – < 11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797
    • affected f78b54e7d83c7879f9a6e49e6724019ca34177cc
    • affected d79d7d5c878809964da537336dad5ff55fa1605e
    • affected 4.9.224 – < 4.9.337
    • affected 3.16.83 – < 3.17
    • affected 4.4.224 – < 4.5
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50282 badge
[![CVE-2022-50282](https://trackcve.app/badge/CVE-2022-50282.svg)](https://trackcve.app/cve/CVE-2022-50282)

Record last updated .