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-50473cpufreq: Init completion before kobject_init_and_add()

Description

In the Linux kernel, the following vulnerability has been resolved: cpufreq: Init completion before kobject_init_and_add() In cpufreq_policy_alloc(), it will call uninitialed completion in cpufreq_sysfs_release() when kobject_init_and_add() fails. And that will cause a crash such as the following page fault in complete: BUG: unable to handle page fault for address: fffffffffffffff8 [..] RIP: 0010:complete+0x98/0x1f0 [..] Call Trace: kobject_put+0x1be/0x4c0 cpufreq_online.cold+0xee/0x1fd cpufreq_add_dev+0x183/0x1e0 subsys_interface_register+0x3f5/0x4e0 cpufreq_register_driver+0x3b7/0x670 acpi_cpufreq_init+0x56c/0x1000 [acpi_cpufreq] do_one_initcall+0x13d/0x780 do_init_module+0x1c3/0x630 load_module+0x6e67/0x73b0 __do_sys_finit_module+0x181/0x240 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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-50473, 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 95% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < 3cdd91a9163248935720927531066b74f57aa43b
    • affected 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < e379b88a8f8cffc99b318e028705ed9e3da0e1e0
    • affected 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < 8fb4c98f20dfca1237de2e3dfdbe78d156784fd3
    • affected 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < d88540acfc7a17079021d866de914112c396edb1
    • affected 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < e7c0c943ed675b66d4bbb16c51c6a3bb58da047e
    • affected 4ebe36c94aed95de71a8ce6a6762226d31c938ee – < 5c51054896bcce1d33d39fead2af73fec24f40b6
    • affected e977b1477a6725868302957e6b5c330220391797
    • affected 5.1.6 – < 5.2
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.87 – ≤ 5.15.*
    • unaffected 6.0.18 – ≤ 6.0.*
    • unaffected 6.1.4 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .