Local kernel crash via stale rtnetlink pointers
Published Jun 20, 2024 · Updated Aug 5, 2026
Use-after-free in Linux kernel rtnetlink 3.14 through 5.16.5 allows local users to crash the kernel through crafted link changes. The __rtnl_newlink() replay loop retains master_dev and m_ops pointers from a preceding attempt, allowing a later iteration to dereference freed objects. A local low-privileged user must reach rtnetlink link-creation handling; exploitation can panic the host, while broader confidentiality or integrity effects are not established by the upstream patch.
Summary
What happened
Use-after-free in Linux kernel rtnetlink 3.14 through 5.16.5 allows local users to crash the kernel through crafted link changes. The __rtnl_newlink() replay loop retains master_dev and m_ops pointers from a preceding attempt, allowing a later iteration to dereference freed objects. A local low-privileged user must reach rtnetlink link-creation handling; exploitation can panic the host, while broader confidentiality or integrity effects are not established by the upstream patch.
The record
- CVE
- CVE-2022-48742
- Published
- Jun 20, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.14
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <2cf180360d66bd657e606c1217e0e668e6faa303
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <36a9a0aee881940476b254e0352581401b23f210
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <3bbe2019dd12b8d13671ee6cda055d49637b4c39
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <7d9211678c0f0624f74cdff36117ab8316697bb8
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <a01e60a1ec6bef9be471fb7182a33c6d6f124e93
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <bd43771ee9759dd9dfae946bff190e2c5a120de5
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <c6f6f2444bdbe0079e41914a35081530d0409963
- Affected versionversion=ba7d49b1f0f8e5f24294a880ed576964059af5ef <def5e7070079b2a214b3b1a2fbec623e6fbfe34a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo