Skip to content
TrackCVE
  • 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-50857

rapidio: rio: fix possible name leak in rio_register_mport()

Not scoredEPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: rapidio: rio: fix possible name leak in rio_register_mport() If device_register() returns error, the name allocated by dev_set_name() need be freed. It should use put_device() to give up the reference in the error path, so that the name can be freed in kobject_cleanup(), and list_del() is called to delete the port from rio_mports.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (7 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 0a71344f99289250e4d5b8adbac76f444485c840
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 117fede82e9d6ea3de30746d500eb5edc2eb8310
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < a73a626c0510d203e369aeb26c4d6ec9c75af027
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 1bbad5793f404cf218757e3beb600eca6080330f
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 97d9eb45ffa67ffa112a6659953321b8f7db0065
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < a47de2fd3f88a7788be19f94ade72c2244a98045
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 4ddbeae5f224d924cf0b12460dda88c7480aa452
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < 9abba4aa60874c5216fc8de7dededadc791de696
    • affected 2aaf308b95b24649a6dcfed89cd956e972089b2a – < e92a216d16bde65d21a3227e0fb2aa0794576525
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • 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-50857 badge
[![CVE-2022-50857](https://trackcve.app/badge/CVE-2022-50857.svg)](https://trackcve.app/cve/CVE-2022-50857)

Record last updated .