All reports
Medium

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

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2022-48742

Probability of exploitation in the next 30 days: 0.24%

FIRST EPSS · 2026-11-18

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.

A flaw was found in the Linux kernel's rtnetlink subsystem. When processing network interface configuration requests, the kernel fails to properly reset internal device references during retry operations in the link creation handler. A local attacker with network administration privileges could exploit this issue to trigger a use-after-free condition (accessing memory after it has been released), leading to a Denial of Service (DoS) through a system crash or potential arbitrary code execution.