net: fix potential refcount leak in ndisc_router_discovery()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.635.19.46.0In the Linux kernel, the following vulnerability has been resolved:
net: fix potential refcount leak in ndisc_router_discovery()
The issue happens on specific paths in the function. After both the object `rt` and `neigh` are grabbed successfully, when `lifetime` is nonzero but the metric needs change, the function just deletes the route and set `rt` to NULL. Then, it may try grabbing `rt` and `neigh` again if above conditions hold. The function simply overwrite `neigh` if succeeds or returns if fails, without decreasing the reference count of previous `neigh`. This may result in memory leaks.
Fix it by decrementing the reference count of `neigh` in place.
From the CVE record · Linux
A reference-count leak in the Linux kernel’s ndisc_router_discovery() can cause memory leaks on specific route-update paths. The input does not specify how an attacker could trigger the issue or whether network access, authentication, or user interaction is required.
Teams running the Linux kernel should check their deployments; affected versions are not specified.