← Back
USN-7704-2
Vulnerability in linux-aws-fips (USN-7704-2)
Summary
vulnerability in linux-aws-fips (USN-7704-2). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.15.0-1090.97+fips1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-7704-2** has been found in linux-aws-fips.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade linux-aws-fips to **5.15.0-1090.97+fips1** or later.
If unsure, ask your IT team or search "linux-aws-fips USN-7704-2" on the vendor's site.
USN-7704-2 (linux-aws-fips) —
Patched: `5.15.0-1090.97+fips1` — 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-fips.
📍 Affected scope
linux-aws-fips — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.15.0-1090.97+fips1**.
🛡️ 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-fips' .` 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-aws-fips' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-aws-fips` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-aws-fips to 5.15.0-1090.97+fips1ステージング環境で 5.15.0-1090.97+fips1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:FIPS-updates:22.04:LTS
linux-aws-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1090.97+fips1"}]}]
Ubuntu:Pro:FIPS-updates:22.04:LTS
linux-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-152.162+fips1"}]}]
Ubuntu:Pro:FIPS-updates:22.04:LTS
linux-gcp-fips
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1090.99+fips1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7704-2
- report https://ubuntu.com/security/CVE-2025-38003
- report https://ubuntu.com/security/CVE-2025-38004
- report https://ubuntu.com/security/CVE-2025-38031
- report https://ubuntu.com/security/CVE-2025-38034
- report https://ubuntu.com/security/CVE-2025-38035
- report https://ubuntu.com/security/CVE-2025-38037
- report https://ubuntu.com/security/CVE-2025-38043
- report https://ubuntu.com/security/CVE-2025-38044
- report https://ubuntu.com/security/CVE-2025-38048
- report https://ubuntu.com/security/CVE-2025-38051
- report https://ubuntu.com/security/CVE-2025-38052
- report https://ubuntu.com/security/CVE-2025-38058
- report https://ubuntu.com/security/CVE-2025-38061
- report https://ubuntu.com/security/CVE-2025-38065
- report https://ubuntu.com/security/CVE-2025-38066
- report https://ubuntu.com/security/CVE-2025-38068
- report https://ubuntu.com/security/CVE-2025-38072
- report https://ubuntu.com/security/CVE-2025-38075
- report https://ubuntu.com/security/CVE-2025-38077
- report https://ubuntu.com/security/CVE-2025-38078
- report https://ubuntu.com/security/CVE-2025-38079