CVE-2022-48742
published 2024-06-20CVE-2022-48742: 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…
PriorityP336high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.24%
15.1th percentile
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.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.7-1 (bookworm) | linux 5.16.7-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < 2cf180360d66bd657e606c1217e0e668e6faa303 | 2cf180360d66bd657e606c1217e0e668e6faa303 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < 7d9211678c0f0624f74cdff36117ab8316697bb8 | 7d9211678c0f0624f74cdff36117ab8316697bb8 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < a01e60a1ec6bef9be471fb7182a33c6d6f124e93 | a01e60a1ec6bef9be471fb7182a33c6d6f124e93 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < bd43771ee9759dd9dfae946bff190e2c5a120de5 | bd43771ee9759dd9dfae946bff190e2c5a120de5 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < 3bbe2019dd12b8d13671ee6cda055d49637b4c39 | 3bbe2019dd12b8d13671ee6cda055d49637b4c39 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < def5e7070079b2a214b3b1a2fbec623e6fbfe34a | def5e7070079b2a214b3b1a2fbec623e6fbfe34a |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < 36a9a0aee881940476b254e0352581401b23f210 | 36a9a0aee881940476b254e0352581401b23f210 |
| linux | linux | >= ba7d49b1f0f8e5f24294a880ed576964059af5ef < c6f6f2444bdbe0079e41914a35081530d0409963 | c6f6f2444bdbe0079e41914a35081530d0409963 |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 3.14 < 4.9.300 | 4.9.300 |
| linux | linux_kernel | >= 4.10 < 4.14.265 | 4.14.265 |
| linux | linux_kernel | >= 4.15 < 4.19.228 | 4.19.228 |
| linux | linux_kernel | >= 4.20 < 5.4.177 | 5.4.177 |
| linux | linux_kernel | >= 5.11 < 5.15.20 | 5.15.20 |
| linux | linux_kernel | >= 5.16 < 5.16.6 | 5.16.6 |
| linux | linux_kernel | >= 5.5 < 5.10.97 | 5.10.97 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
vendor_redhat·2024-06-20·CVSS 7.8
CVE-2022-48742 [HIGH] CWE-416 kernel: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
kernel: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
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.
Statement: Actual only for Red Hat Enterprise Linux 8.
Fixed for all versions of Red Hat Enterprise Linux 9.
Reading the source code, related source in function __rtnl_newlink or in rtnl_newlink for newer versions.
The fix is that setting to NULL these vars
+master_dev = NULL;
+m_ops = NULL;
just before usage (before call "master_dev = netdev_master_upper_dev_get(d
Debian
CVE-2022-48742: linux - In the Linux kernel, the following vulnerability has been resolved: rtnetlink: ...
vendor_debian·2022·CVSS 7.8
CVE-2022-48742 [HIGH] CVE-2022-48742: linux - In the Linux kernel, the following vulnerability has been resolved: rtnetlink: ...
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.
Scope: local
bookworm: resolved (fixed in 5.16.7-1)
bullseye: resolved (fixed in 5.10.103-1)
forky: resolved (fixed in 5.16.7-1)
sid: resolved (fixed in 5.16.7-1)
trixie: resolved (fixed in 5.16.7-1)
GHSA
GHSA-qg8q-9c83-3485: In the Linux kernel, the following vulnerability has been resolved:
rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
While looki
ghsa_unreviewed·2024-06-20
CVE-2022-48742 [HIGH] CWE-416 GHSA-qg8q-9c83-3485: In the Linux kernel, the following vulnerability has been resolved:
rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
While looki
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.
OSV
CVE-2022-48742: In the Linux kernel, the following vulnerability has been resolved: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() While looking
osv·2024-06-20·CVSS 7.8
CVE-2022-48742 [HIGH] CVE-2022-48742: In the Linux kernel, the following vulnerability has been resolved: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() While looking
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/2cf180360d66bd657e606c1217e0e668e6faa303https://git.kernel.org/stable/c/36a9a0aee881940476b254e0352581401b23f210https://git.kernel.org/stable/c/3bbe2019dd12b8d13671ee6cda055d49637b4c39https://git.kernel.org/stable/c/7d9211678c0f0624f74cdff36117ab8316697bb8https://git.kernel.org/stable/c/a01e60a1ec6bef9be471fb7182a33c6d6f124e93https://git.kernel.org/stable/c/bd43771ee9759dd9dfae946bff190e2c5a120de5https://git.kernel.org/stable/c/c6f6f2444bdbe0079e41914a35081530d0409963https://git.kernel.org/stable/c/def5e7070079b2a214b3b1a2fbec623e6fbfe34ahttps://git.kernel.org/stable/c/2cf180360d66bd657e606c1217e0e668e6faa303https://git.kernel.org/stable/c/36a9a0aee881940476b254e0352581401b23f210https://git.kernel.org/stable/c/3bbe2019dd12b8d13671ee6cda055d49637b4c39https://git.kernel.org/stable/c/7d9211678c0f0624f74cdff36117ab8316697bb8https://git.kernel.org/stable/c/a01e60a1ec6bef9be471fb7182a33c6d6f124e93https://git.kernel.org/stable/c/bd43771ee9759dd9dfae946bff190e2c5a120de5https://git.kernel.org/stable/c/c6f6f2444bdbe0079e41914a35081530d0409963https://git.kernel.org/stable/c/def5e7070079b2a214b3b1a2fbec623e6fbfe34a
2024-06-20
Published