Vulnerability in Kernel (CVE-2022-50513)

Summary

Vulnerability in Kernel (CVE-2022-50513). Risk of unauthorized operations or information disclosure. Exploitable via exit. Mitigation: upgrade to 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()

In rtw_init_cmd_priv(), if pcmdpriv->rsp_allocated_buf is allocated
in failure, then pcmdpriv->cmd_allocated_buf will be not properly
released. Besides, considering there are only two error paths and the
first one can directly return, so we do not need implicitly jump to the
exit tag to execute the error handler.

So this patch added kfree(pcmdpriv->cmd_allocated_buf); on the error
path to release the resource and simplified the return logic of
rtw_init_cmd_priv(). As there is no proper device to test with, no runtime
testing was performed.

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-50513 has been found in Kernel.
Attackers can target a specific entry point like exit over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-50513" on the vendor's site.

CVE-2022-50513 (Kernel)
Attack surface: exit
Patched: 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 — 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 exit.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: exit.

🔥 Severity

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

🔧 How to fix

Update to 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3.

🛡️ 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
Identify exposure identify
```
grep -r 'Kernel' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Kernel to 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3
```
ステージング環境で 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"4.12.0"},{"fixed":"5.4.220"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.150"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.75"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.20.0"},{"fixed":"6.0.3"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2022-50513 linux Fixed in: 5.10.158-1
Ubuntu UBUNTU-CVE-2022-50513 linux