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-49021net: phy: fix null-ptr-deref while probe() failed

Description

In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: <TASK> klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it's failed, driver is not bound device_bind_driver() // probe failed, it's not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev->drv is not NULL klist_remove() <- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the 'dev->driver', probe() fails, device_bind_driver() is not called, so the knode_driver->n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev->driver to NULL in the error path in phy_attach_direct().

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 19 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-49021, 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 (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 e13934563db047043ccead26412f552375cea90c – < 8aaafe0f71314f46a066382a047ba8bb3840d273
    • affected e13934563db047043ccead26412f552375cea90c – < 51d7f6b20fae8bae64ad1136f1e30d1fd5ba78f7
    • affected e13934563db047043ccead26412f552375cea90c – < 0744c7be4de564db03e24527b2e096b7e0e20972
    • affected e13934563db047043ccead26412f552375cea90c – < 3e21f85d87c836462bb52ef2078ea561260935c1
    • affected e13934563db047043ccead26412f552375cea90c – < fe6bc99c27c21348f548966118867ed26a9a372c
    • affected e13934563db047043ccead26412f552375cea90c – < 7730904f50c7187dd16c76949efb56b5fb55cd57
    • affected e13934563db047043ccead26412f552375cea90c – < eaa5722549ac2604ffa56c2e946acc83226f130c
    • affected e13934563db047043ccead26412f552375cea90c – < 369eb2c9f1f72adbe91e0ea8efb130f0a2ba11a6
  • Linux · Linux

    • affected 2.6.14
    • unaffected < 2.6.14
    • unaffected 4.9.335 – ≤ 4.9.*
    • unaffected 4.14.301 – ≤ 4.14.*
    • unaffected 4.19.268 – ≤ 4.19.*
    • unaffected 5.4.226 – ≤ 5.4.*
    • unaffected 5.10.158 – ≤ 5.10.*
    • unaffected 5.15.82 – ≤ 5.15.*
    • unaffected 6.0.12 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .