Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is an error-handling bug in character-device registration. Under an injected device_add() failure path, cleanup can call kobject_put() on an uninitialized object, causing a kernel warning. The provided sources do not show remote exploitation, privilege impact, or data exposure.
Executive priority
Treat as a kernel maintenance item unless your environment has unusual exposure through custom drivers or unsupported kernels. There is insufficient source evidence to rank it as urgent exploitation-driven work, but kernel updates should remain scheduled and tracked.
Technical view
cdev_device_add() may enter an incorrect error path when device_add() fails and dev->devt is unset. In that case cdev_add() was not called, so cdev_del() should not run. The fix checks dev->devt before cleanup. Evidence comes from Linux stable commits and the CVE record.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions or downstream kernels carrying the vulnerable chardev code. The bundle lists Linux kernel versions including 4.12, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, and 6.2.
Exploitation context
The source bundle describes discovery during fault-injection testing, not real-world exploitation. KEV status is false, and no cited source reports active exploitation, weaponized use, or a practical attack path.
Researcher notes
The provided evidence is narrow: a warning triggered by fault injection and a cleanup-path correction. Impact boundaries, attacker prerequisites, and exploitability are not established in the bundle. Validate by source diff review and downstream backport confirmation, not by assuming CVSS-like severity.
Mitigation direction
- Map running kernels against the CVE record and vendor kernel advisories.
- Apply Linux stable or distribution kernel updates containing the referenced fixes.
- Prioritize hosts using custom kernels or device-driver-heavy workloads for review.
- If patch timing is uncertain, follow your Linux distribution vendor guidance.
Validation and detection
- Record kernel versions across servers, containers hosts, appliances, and embedded Linux assets.
- Confirm installed kernel packages include the relevant stable fix or vendor backport.
- Review kernel logs for related kobject or cdev_device_add warnings.
- Track remediation status by kernel lineage, not only distribution version.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit 5d2146889fad
- Linux stable commit 6acf8597c5b0
- Linux stable commit 34d17b39bcee
- Linux stable commit d85b5247a793
- Linux stable commit c46db6088bcc
- Linux stable commit 28dc61cc49c6
- Linux stable commit b5de1eac71fe
- Linux stable commit 85a5660491b5
- Linux stable commit 11fa7fefe3d8
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-50282 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/5d2146889fad4cb9e6c13e790d4cfd871486eca8CVE reference, Linux
- https://git.kernel.org/stable/c/6acf8597c5b04f455ee0649e11e5f3bcd28f381eCVE reference, Linux
- https://git.kernel.org/stable/c/34d17b39bceef25e4cf9805cd59250ae05d0a139CVE reference, Linux
- https://git.kernel.org/stable/c/d85b5247a79355b8432bfd9ac871f96117f750d4CVE reference, Linux
- https://git.kernel.org/stable/c/c46db6088bccff5115674d583fef46ede80077a2CVE reference, Linux
- https://git.kernel.org/stable/c/28dc61cc49c6e995121c6d86bef4b73df78dda80CVE reference, Linux
- https://git.kernel.org/stable/c/b5de1eac71fec1af7723f1083d23a24789fd795cCVE reference, Linux
- https://git.kernel.org/stable/c/85a5660491b507d33662b8e81c142e6041e642ebCVE reference, Linux
- https://git.kernel.org/stable/c/11fa7fefe3d8fac7da56bc9aa3dd5fb3081ca797CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.