← Back
USN-7585-6
Vulnerability in linux-bluefield (USN-7585-6)
Summary
vulnerability in linux-bluefield (USN-7585-6). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.4.0-1106.113` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-7585-6** has been found in linux-bluefield.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade linux-bluefield to **5.4.0-1106.113** or later.
If unsure, ask your IT team or search "linux-bluefield USN-7585-6" on the vendor's site.
USN-7585-6 (linux-bluefield) —
Patched: `5.4.0-1106.113` — 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-bluefield.
📍 Affected scope
linux-bluefield — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.4.0-1106.113**.
🛡️ 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-bluefield' .` 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-bluefield' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-bluefield` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-bluefield to 5.4.0-1106.113ステージング環境で 5.4.0-1106.113 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:20.04:LTS
linux-bluefield
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1106.113"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7585-6
- report https://ubuntu.com/security/CVE-2021-47211
- report https://ubuntu.com/security/CVE-2022-49636
- report https://ubuntu.com/security/CVE-2023-53034
- report https://ubuntu.com/security/CVE-2024-53168
- report https://ubuntu.com/security/CVE-2024-56551
- report https://ubuntu.com/security/CVE-2024-58093
- report https://ubuntu.com/security/CVE-2025-2312
- report https://ubuntu.com/security/CVE-2025-21956
- report https://ubuntu.com/security/CVE-2025-21957
- report https://ubuntu.com/security/CVE-2025-21959
- report https://ubuntu.com/security/CVE-2025-21991
- report https://ubuntu.com/security/CVE-2025-21992
- report https://ubuntu.com/security/CVE-2025-21993
- report https://ubuntu.com/security/CVE-2025-21996
- report https://ubuntu.com/security/CVE-2025-22004
- report https://ubuntu.com/security/CVE-2025-22005
- report https://ubuntu.com/security/CVE-2025-22007
- report https://ubuntu.com/security/CVE-2025-22018
- report https://ubuntu.com/security/CVE-2025-22020
- report https://ubuntu.com/security/CVE-2025-22021
- report https://ubuntu.com/security/CVE-2025-22035
- report https://ubuntu.com/security/CVE-2025-22045
- report https://ubuntu.com/security/CVE-2025-22054
- report https://ubuntu.com/security/CVE-2025-22063
- report https://ubuntu.com/security/CVE-2025-22071
- report https://ubuntu.com/security/CVE-2025-22073
- report https://ubuntu.com/security/CVE-2025-22079
- report https://ubuntu.com/security/CVE-2025-22086
- report https://ubuntu.com/security/CVE-2025-23136
- report https://ubuntu.com/security/CVE-2025-37937
- report https://ubuntu.com/security/CVE-2025-38637
- report https://ubuntu.com/security/CVE-2025-39735