CVE-2022-48742
rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.14
References 8
git.kernel.org
- stable/c/2cf180360d66bd657e606c1217e0e668e6faa303
- stable/c/7d9211678c0f0624f74cdff36117ab8316697bb8
- stable/c/a01e60a1ec6bef9be471fb7182a33c6d6f124e93
- stable/c/bd43771ee9759dd9dfae946bff190e2c5a120de5
- stable/c/3bbe2019dd12b8d13671ee6cda055d49637b4c39
- stable/c/def5e7070079b2a214b3b1a2fbec623e6fbfe34a
- stable/c/36a9a0aee881940476b254e0352581401b23f210
- stable/c/c6f6f2444bdbe0079e41914a35081530d0409963