← Back
USN-7699-1
Vulnerability in linux-aws-6.14 (USN-7699-1)
Summary
vulnerability in linux-aws-6.14 (USN-7699-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6.14.0-1011.11~24.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-7699-1** has been found in linux-aws-6.14.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade linux-aws-6.14 to **6.14.0-1011.11~24.04.1** or later.
If unsure, ask your IT team or search "linux-aws-6.14 USN-7699-1" on the vendor's site.
USN-7699-1 (linux-aws-6.14) —
Patched: `6.14.0-1011.11~24.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-aws-6.14.
📍 Affected scope
linux-aws-6.14 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.14.0-1011.11~24.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-aws-6.14' .` 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-6.14' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-aws-6.14` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-aws-6.14 to 6.14.0-1011.11~24.04.1ステージング環境で 6.14.0-1011.11~24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:24.04:LTS
linux-aws-6.14
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1011.11~24.04.1"}]}]
Ubuntu:24.04:LTS
linux-gcp-6.14
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1014.15~24.04.1"}]}]
Ubuntu:24.04:LTS
linux-oracle-6.14
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.14.0-1011.11~24.04.1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7699-1
- report https://ubuntu.com/security/CVE-2025-37965
- report https://ubuntu.com/security/CVE-2025-37947
- report https://ubuntu.com/security/CVE-2025-37948
- report https://ubuntu.com/security/CVE-2025-37949
- report https://ubuntu.com/security/CVE-2025-37950
- report https://ubuntu.com/security/CVE-2025-37951
- report https://ubuntu.com/security/CVE-2025-37952
- report https://ubuntu.com/security/CVE-2025-37954
- report https://ubuntu.com/security/CVE-2025-37955
- report https://ubuntu.com/security/CVE-2025-37956
- report https://ubuntu.com/security/CVE-2025-37957
- report https://ubuntu.com/security/CVE-2025-37958
- report https://ubuntu.com/security/CVE-2025-37959
- report https://ubuntu.com/security/CVE-2025-37960
- report https://ubuntu.com/security/CVE-2025-37961
- report https://ubuntu.com/security/CVE-2025-37962
- report https://ubuntu.com/security/CVE-2025-37963
- report https://ubuntu.com/security/CVE-2025-37964
- report https://ubuntu.com/security/CVE-2025-37966
- report https://ubuntu.com/security/CVE-2025-37967
- report https://ubuntu.com/security/CVE-2025-37968
- report https://ubuntu.com/security/CVE-2025-37969
- report https://ubuntu.com/security/CVE-2025-37970
- report https://ubuntu.com/security/CVE-2025-37971
- report https://ubuntu.com/security/CVE-2025-37972
- report https://ubuntu.com/security/CVE-2025-37973
- report https://ubuntu.com/security/CVE-2025-37992
- report https://ubuntu.com/security/CVE-2025-37993
- report https://ubuntu.com/security/CVE-2025-37994
- report https://ubuntu.com/security/CVE-2025-37995
- report https://ubuntu.com/security/CVE-2025-37996
- report https://ubuntu.com/security/CVE-2025-37998
- report https://ubuntu.com/security/CVE-2025-37999
- report https://ubuntu.com/security/CVE-2025-38002
- report https://ubuntu.com/security/CVE-2025-38005
- report https://ubuntu.com/security/CVE-2025-38006
- report https://ubuntu.com/security/CVE-2025-38007
- report https://ubuntu.com/security/CVE-2025-38008
- report https://ubuntu.com/security/CVE-2025-38009
- report https://ubuntu.com/security/CVE-2025-38010
- report https://ubuntu.com/security/CVE-2025-38011
- report https://ubuntu.com/security/CVE-2025-38012
- report https://ubuntu.com/security/CVE-2025-38013
- report https://ubuntu.com/security/CVE-2025-38014
- report https://ubuntu.com/security/CVE-2025-38015
- report https://ubuntu.com/security/CVE-2025-38016
- report https://ubuntu.com/security/CVE-2025-38018
- report https://ubuntu.com/security/CVE-2025-38019
- report https://ubuntu.com/security/CVE-2025-38020
- report https://ubuntu.com/security/CVE-2025-38021
- report https://ubuntu.com/security/CVE-2025-38022
- report https://ubuntu.com/security/CVE-2025-38023
- report https://ubuntu.com/security/CVE-2025-38024
- report https://ubuntu.com/security/CVE-2025-38025
- report https://ubuntu.com/security/CVE-2025-38027
- report https://ubuntu.com/security/CVE-2025-38028
- report https://ubuntu.com/security/CVE-2025-38056
- report https://ubuntu.com/security/CVE-2025-38094
- report https://ubuntu.com/security/CVE-2025-38095