Categories
CVE-2022-50043

Vulnerability in Kernel (CVE-2022-50043)

Summary

Vulnerability in Kernel (CVE-2022-50043). Risk of unauthorized operations or information disclosure. Exploitable via neigh. Mitigation: upgrade to 5.15.63, 5.19.4 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-50043 has been found in Kernel.
Attackers can target a specific entry point like neigh over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 5.15.63, 5.19.4 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-50043" on the vendor's site.

CVE-2022-50043 (Kernel)
Attack surface: neigh / lifetime
Patched: 5.15.63, 5.19.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Kernel. Attackers reach the vulnerable code path via neigh.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: neigh / lifetime.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.15.63, 5.19.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'Kernel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade Kernel to 5.15.63, 5.19.4

    ステージング環境で 5.15.63, 5.19.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"5.12.0"},{"fixed":"5.15.63"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details