Vulnerability in Kernel (CVE-2022-50367)

Summary

Vulnerability in Kernel (CVE-2022-50367). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.9.331, 4.14.296, 4.19.262, 5.4.218, 5.10.148, 5.15.73, 5.19.15, 6.0.1 or later.

Original description

The description as published by the source.

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

fs: fix UAF/GPF bug in nilfs_mdt_destroy

In alloc_inode, inode_init_always() could return -ENOMEM if
security_inode_alloc() fails, which causes inode->i_private
uninitialized. Then nilfs_is_metadata_file_inode() returns
true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(),
which frees the uninitialized inode->i_private
and leads to crashes(e.g., UAF/GPF).

Fix this by moving security_inode_alloc just prior to
this_cpu_inc(nr_inodes)

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-50367 has been found in Kernel.
Successful exploitation can lead to full system takeover.
What to do: upgrade Kernel to 4.9.331, 4.14.296, 4.19.262, 5.4.218, 5.10.148, 5.15.73, 5.19.15, 6.0.1 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-50367" on the vendor's site.

CVE-2022-50367 (Kernel)
Attack vector: local / no user interaction
Patched: 4.9.331, 4.14.296, 4.19.262, 5.4.218, 5.10.148, 5.15.73, 5.19.15, 6.0.1 — 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: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.9.331, 4.14.296, 4.19.262, 5.4.218, 5.10.148, 5.15.73, 5.19.15, 6.0.1.

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

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.12"},{"fixed":"4.9.331"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.10.0"},{"fixed":"4.14.296"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.15.0"},{"fixed":"4.19.262"}]},{"type":"ECOSYSTEM","events":[{"introduced":"4.20.0"},{"fixed":"5.4.218"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.5.0"},{"fixed":"5.10.148"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.73"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.15"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.20.0"},{"fixed":"6.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2022-50367 linux Fixed in: 5.10.148-1
Ubuntu UBUNTU-CVE-2022-50367 linux-azure Fixed in: 4.15.0-1157.172~14.04.2