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-49350net: mdio: unexport __init-annotated mdio_bus_init()

Description

In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 15 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-49350, 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.28% · top 79% of all CVEs (17 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 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < ab64ec2c75683f30ccde9eaaf0761002f901aa12
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < 5534bcd7c40299862237c4a8fd9c5031b3db1538
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < 6a90a44d53428a3bf01bd80df9ba78b19959270c
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < 7759c3222815b945a94b212bc0c6cdec475cfec2
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < 59fa94cddf9eef8d8dae587373eed8b8f4eb11d7
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < f5c68137f1191ba3fcf6260ec71b30be2e2bf4c3
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < f2f0f8c18b60ca64ff50892ed899cf1c77864755
    • affected 90eff9096c01ba90cdae504a6b95ee87fe2556a3 – < 35b42dce619701f1300fb8498dae82c9bb1f0263
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.14.283 – ≤ 4.14.*
    • unaffected 4.19.247 – ≤ 4.19.*
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.122 – ≤ 5.10.*
    • unaffected 5.15.47 – ≤ 5.15.*
    • unaffected 5.17.15 – ≤ 5.17.*
    • unaffected 5.18.4 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .