← Back
USN-6185-1

Vulnerability in linux-aws (USN-6185-1)

Summary

vulnerability in linux-aws (USN-6185-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.4.0-1104.112` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-6185-1** has been found in linux-aws. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade linux-aws to **5.4.0-1104.112** or later. If unsure, ask your IT team or search "linux-aws USN-6185-1" on the vendor's site.
USN-6185-1 (linux-aws) — Patched: `5.4.0-1104.112` — 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-aws.
📍 Affected scope
linux-aws — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.4.0-1104.112**.
🛡️ 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-aws' .` 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

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

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

  2. 6
    Apply patch patch
    Upgrade linux-aws to 5.4.0-1104.112

    ステージング環境で 5.4.0-1104.112 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

Ubuntu:20.04:LTS linux-aws
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1104.112"}]}]
Ubuntu:20.04:LTS linux-azure
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1110.116"}]}]
Ubuntu:20.04:LTS linux-bluefield
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1065.71"}]}]
Ubuntu:20.04:LTS linux-gcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1107.116"}]}]
Ubuntu:20.04:LTS linux-gke
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1102.109"}]}]
Ubuntu:20.04:LTS linux-gkeop
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1071.75"}]}]
Ubuntu:20.04:LTS linux-ibm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1051.56"}]}]
Ubuntu:20.04:LTS linux-kvm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1093.99"}]}]
Ubuntu:20.04:LTS linux-oracle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1103.112"}]}]
Ubuntu:20.04:LTS linux-raspi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1088.99"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →