CVE-2022-50043
net: fix potential refcount leak in ndisc_router_discovery()
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 6b2e04bc240fe9be9e690059f710e9f95346d34d; < ffb15594433391fd7885eb88ce5a7f7bdeefbb15 (affected, git) ≥ 6b2e04bc240fe9be9e690059f710e9f95346d34d; < 7998043d31d000c3a93f46182e6569dd0eecda34 (affected, git) ≥ 6b2e04bc240fe9be9e690059f710e9f95346d34d; < 7396ba87f1edf549284869451665c7c4e74ecd4f (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.12 (affected) ≥ 0; < 5.12 (unaffected, semver) ≥ 5.15.63; ≤ 5.15.* (unaffected, semver) ≥ 5.19.4; ≤ 5.19.* (unaffected, semver) ≥ 6.0; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.