Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48742

rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()

High7.8EPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() While looking at one unrelated syzbot bug, I found the replay logic in __rtnl_newlink() to potentially trigger use-after-free. It is better to clear master_dev and m_ops inside the loop, in case we have to replay it.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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-48742, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (7 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: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < 2cf180360d66bd657e606c1217e0e668e6faa303
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < 7d9211678c0f0624f74cdff36117ab8316697bb8
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < a01e60a1ec6bef9be471fb7182a33c6d6f124e93
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < bd43771ee9759dd9dfae946bff190e2c5a120de5
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < 3bbe2019dd12b8d13671ee6cda055d49637b4c39
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < def5e7070079b2a214b3b1a2fbec623e6fbfe34a
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < 36a9a0aee881940476b254e0352581401b23f210
    • affected ba7d49b1f0f8e5f24294a880ed576964059af5ef – < c6f6f2444bdbe0079e41914a35081530d0409963
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 4.9.300 – ≤ 4.9.*
    • unaffected 4.14.265 – ≤ 4.14.*
    • unaffected 4.19.228 – ≤ 4.19.*
    • unaffected 5.4.177 – ≤ 5.4.*
    • unaffected 5.10.97 – ≤ 5.10.*
    • unaffected 5.15.20 – ≤ 5.15.*
    • unaffected 5.16.6 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (8)

Sources

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

Badge for a README or a ticket

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

Record last updated .