Vulnerability in Kernel (CVE-2022-49013)

Summary

Vulnerability in Kernel (CVE-2022-49013). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.4.226, 5.10.158, 5.15.82, 6.0.12 or later.

Original description

The description as published by the source.

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

sctp: fix memory leak in sctp_stream_outq_migrate()

When sctp_stream_outq_migrate() is called to release stream out resources,
the memory pointed to by prio_head in stream out is not released.

The memory leak information is as follows:
unreferenced object 0xffff88801fe79f80 (size 64):
comm "sctp_repo", pid 7957, jiffies 4294951704 (age 36.480s)
hex dump (first 32 bytes):
80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff ................
90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff ................
backtrace:
[] kmalloc_trace+0x26/0x60
[] sctp_sched_prio_set+0x4cc/0x770
[] sctp_stream_init_ext+0xd2/0x1b0
[] sctp_sendmsg_to_asoc+0x1614/0x1a30
[] sctp_sendmsg+0xda1/0x1ef0
[] inet_sendmsg+0x9d/0xe0
[] sock_sendmsg+0xd3/0x120
[] __sys_sendto+0x23a/0x340
[] __x64_sys_sendto+0xe1/0x1b0
[] do_syscall_64+0x39/0xb0
[] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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-49013 has been found in Kernel.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 5.4.226, 5.10.158, 5.15.82, 6.0.12 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-49013" on the vendor's site.

CVE-2022-49013 (Kernel)
Patched: 5.4.226, 5.10.158, 5.15.82, 6.0.12 — 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.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel.

🔥 Severity

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

🔧 How to fix

Update to 5.4.226, 5.10.158, 5.15.82, 6.0.12.

🛡️ 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.226, 5.10.158, 5.15.82, 6.0.12
```
ステージング環境で 5.4.226, 5.10.158, 5.15.82, 6.0.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"4.15.0"},{"fixed":"5.4.226"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.158"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.82"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.0.12"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

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