Answer in brief
CVE-2022-48742 records a High severity (CVSS 7.8) vulnerability in rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-48742 records a High severity (CVSS 7.8) vulnerability in rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <2cf180360d66bd657e606c1217e0e668e6faa303 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <7d9211678c0f0624f74cdff36117ab8316697bb8 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <a01e60a1ec6bef9be471fb7182a33c6d6f124e93 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <bd43771ee9759dd9dfae946bff190e2c5a120de5 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <3bbe2019dd12b8d13671ee6cda055d49637b4c39 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <def5e7070079b2a214b3b1a2fbec623e6fbfe34a || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <36a9a0aee881940476b254e0352581401b23f210 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <c6f6f2444bdbe0079e41914a35081530d0409963 | 2cf180360d66bd657e606c1217e0e668e6faa303, 7d9211678c0f0624f74cdff36117ab8316697bb8, a01e60a1ec6bef9be471fb7182a33c6d6f124e93, bd43771ee9759dd9dfae946bff190e2c5a120de5, 3bbe2019dd12b8d13671ee6cda055d49637b4c39, def5e7070079b2a214b3b1a2fbec623e6fbfe34a, 36a9a0aee881940476b254e0352581401b23f210, c6f6f2444bdbe0079e41914a35081530d0409963 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Jun 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <2cf180360d66bd657e606c1217e0e668e6faa303 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <7d9211678c0f0624f74cdff36117ab8316697bb8 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <a01e60a1ec6bef9be471fb7182a33c6d6f124e93 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <bd43771ee9759dd9dfae946bff190e2c5a120de5 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <3bbe2019dd12b8d13671ee6cda055d49637b4c39 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <def5e7070079b2a214b3b1a2fbec623e6fbfe34a || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <36a9a0aee881940476b254e0352581401b23f210 || >=ba7d49b1f0f8e5f24294a880ed576964059af5ef <c6f6f2444bdbe0079e41914a35081530d0409963 | 2cf180360d66bd657e606c1217e0e668e6faa303, 7d9211678c0f0624f74cdff36117ab8316697bb8, a01e60a1ec6bef9be471fb7182a33c6d6f124e93, bd43771ee9759dd9dfae946bff190e2c5a120de5, 3bbe2019dd12b8d13671ee6cda055d49637b4c39, def5e7070079b2a214b3b1a2fbec623e6fbfe34a, 36a9a0aee881940476b254e0352581401b23f210, c6f6f2444bdbe0079e41914a35081530d0409963 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Jun 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.