Answer in brief
CVE-2022-50043 records a Medium severity (CVSS 5.5) vulnerability in net: fix potential refcount leak in ndisc_router_discovery(). 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 5.5. 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 |
| cpe:2.3:o:linux:linux_kernel:6.0:rc1:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6b2e04bc240fe9be9e690059f710e9f95346d34d <ffb15594433391fd7885eb88ce5a7f7bdeefbb15 || >=6b2e04bc240fe9be9e690059f710e9f95346d34d <7998043d31d000c3a93f46182e6569dd0eecda34 || >=6b2e04bc240fe9be9e690059f710e9f95346d34d <7396ba87f1edf549284869451665c7c4e74ecd4f | ffb15594433391fd7885eb88ce5a7f7bdeefbb15, 7998043d31d000c3a93f46182e6569dd0eecda34, 7396ba87f1edf549284869451665c7c4e74ecd4f |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.