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-50462MIPS: vpe-mt: fix possible memory leak while module exiting

Description

In the Linux kernel, the following vulnerability has been resolved: MIPS: vpe-mt: fix possible memory leak while module exiting Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, it need be freed when module exiting, call put_device() to give up reference, so that it can be freed in kobject_cleanup() when the refcount hit to 0. The vpe_device is static, so remove kfree() from vpe_device_release().

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-50462, 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.16% · top 94% of all CVEs (15 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 1fa5ae857bb14f6046205171d98506d8112dd74e – < 170e9913c2ed5cfc37c0adf0fdbd368d2d8d8168
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 9d180e0bb21c57bd6cca2adeb672d3b522e910b5
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 851ae5640875f06494e40002cd503b11a634c6fb
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < b3325a443525e3b89151879b834519b21c5e3011
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 48d42f4464d713fbdd79f334fdcd6e5be534cc67
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < e820a8192ff68570100347855b567512aec43819
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < b191dde84e40624d5577f64db0ec922c5c0ec57c
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < ab3d47c1fd0202821abd473ca87580faafd47847
    • affected 1fa5ae857bb14f6046205171d98506d8112dd74e – < 5822e8cc84ee37338ab0bdc3124f6eec04dc232d
  • Linux · Linux

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

Record last updated .