← Back
UBUNTU-CVE-2019-15223
Vulnerability in linux (UBUNTU-CVE-2019-15223)
Summary
vulnerability in linux (UBUNTU-CVE-2019-15223). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.0.0-1022.23~18.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2019-15223** has been found in linux.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade linux to **5.0.0-1022.23~18.04.1** or later.
If unsure, ask your IT team or search "linux UBUNTU-CVE-2019-15223" on the vendor's site.
UBUNTU-CVE-2019-15223 (linux) —
Attack vector: physical / unauthenticated / no user interaction
Patched: `5.0.0-1022.23~18.04.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 linux.
📍 Affected scope
linux — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.0.0-1022.23~18.04.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 'linux' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'linux' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux to 5.0.0-1022.23~18.04.1ステージング環境で 5.0.0-1022.23~18.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:14.04:LTS
linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:14.04:LTS
linux-aws
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:14.04:LTS
linux-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:14.04:LTS
linux-lts-xenial
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:18.04:LTS
linux-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.0-1022.23~18.04.1"}]}]
Ubuntu:18.04:LTS
linux-gke-5.0
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.0-1020.20~18.04.1"}]}]
Ubuntu:18.04:LTS
linux-hwe
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.0-31.33~18.04.1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-4147-1
- report https://ubuntu.com/security/CVE-2019-15223
- report https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.8
- report https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0b074ab7fc0d575247b9cc9f93bb7e007ca38840
- report https://syzkaller.appspot.com/bug?id=0c1e517c657d3de2361cb0cc2d3a8663c25039a7
- report https://www.cve.org/CVERecord?id=CVE-2019-15223