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-50251mmc: vub300: fix return value check of mmc_add_host()

Description

In the Linux kernel, the following vulnerability has been resolved: mmc: vub300: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in the remove path. So fix this by checking the return value and goto error path which will call mmc_free_host(), besides, the timer added before mmc_add_host() needs be del. And this patch fixes another missing call mmc_free_host() if usb_control_msg() fails.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 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-50251, 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.17% · top 93% 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 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 41ed46bdbd2878cd6567abe0974a445f8b1b8ec8
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 25f05d762ca5e1c685002a53dd44f68e78ca3feb
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < a46e681151bbdacdf6b89ee8c4e5bad0555142bb
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 3b29f8769d32016b2d89183db4d80c7a71b7e35e
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 3049a3b927a40d89d4582ff1033cd7953be773c7
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < afc898019e7bf18c5eb7a0ac19852fcb1b341b3c
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < c9e85979b59cb86f0a15defa8199d740e2b36b90
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 2044b2ea77945f372ef161d1bbf814e471767ff2
    • affected 88095e7b473a3d9ec3b9c60429576e9cbd327c89 – < 0613ad2401f88bdeae5594c30afe318e93b14676
  • Linux · Linux

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

Record last updated .