Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50547media: solo6x10: fix possible memory leak in solo_sysfs_init()

Description

In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: fix possible memory leak in solo_sysfs_init() If device_register() returns error in solo_sysfs_init(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50547, 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.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 83d4b1ae98a47a739fa5241300b86eb1110d5d63
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < b61509093e1af69e336a094d439b8e1137cb40d8
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 963729538674be4cb8fa292529ecf32de0d6c6dd
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 7b02c50d3978840781808e13bc13137fb81286b5
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 49060c0da57a381563e482e331dc9d4c3725b41b
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 7cf71bbe5d2ee12613f6e278888f5fc9c5c0cc2b
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < d6db105bcfbdbbbd484e788a0ddf8140a4a8c486
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 9416861170ba0da8ddb0f4fd2d28334f0ed3b9c2
    • affected dcae5dacbce518513abf7776cb450b7bd95d722b – < 7f5866dd96d95b74e439f6ee17b8abd8195179fb
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • 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

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .