Vulnérabilité dans linux-azure-fips (USN-7597-2)

Résumé

vulnérabilité dans linux-azure-fips (USN-7597-2). Risque d'opérations non autorisées ou de divulgation. Atténuation : mise à jour vers `5.15.0-1091.100+fips1` ou plus.

Résumé IA snake-internal / snake-material-v2

Une vulnérabilité référencée **USN-7597-2** a été découverte dans linux-azure-fips. Risque d'opérations non autorisées ou de divulgation. Score CVSS : ?/10. Action : mettez à jour linux-azure-fips vers **5.15.0-1091.100+fips1** ou supérieur. En cas de doute, contactez votre service informatique ou cherchez « linux-azure-fips USN-7597-2 » sur le site de l'éditeur.

USN-7597-2 (linux-azure-fips) — Correctif : `5.15.0-1091.100+fips1` — appliquer immédiatement Plan : 1) Audit SBOM, 2) Mise à jour staging→prod, 3) Surveillance WAF/proxy sur les endpoints affectés, 4) Recherche d'IOC dans les logs. Réfs : voir GHSA / avis éditeur / version corrigée liés sur cette page.

❓ Quel est le problème

Une **vulnérabilité** (non classée) affecte linux-azure-fips.

📍 Périmètre concerné

linux-azure-fips — .

🔥 Gravité

Gravité : ?. Risque d'opérations non autorisées ou de divulgation

🔧 Comment corriger

Mettre à jour vers **5.15.0-1091.100+fips1**.

🛡️ Contournement

En attendant le correctif : désactivez la fonctionnalité concernée, appliquez des règles WAF, ou restreignez l'accès par ACL réseau.

🔍 Détection

Recherchez dans les logs des requêtes correspondant aux IOC connus de cette CVE. Auditez les SBOM/dépendances.

Actions de réponse (7 étapes)

Étapes concrètes et exemples de commandes que les équipes SOC/SRE doivent exécuter dans l'ordre

1
Identify exposure identify
```
grep -r 'linux-azure-fips' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-azure-fips` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade linux-azure-fips to 5.15.0-1091.100+fips1
```
ステージング環境で 5.15.0-1091.100+fips1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Paquets affectés

Ubuntu:Pro:FIPS-updates:22.04:LTS linux-azure-fips

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1091.100+fips1"}]}]

Références

advisory https://ubuntu.com/security/notices/USN-7597-2
report https://ubuntu.com/security/CVE-2022-49636
report https://ubuntu.com/security/CVE-2022-49728
report https://ubuntu.com/security/CVE-2023-53034
report https://ubuntu.com/security/CVE-2024-8805
report https://ubuntu.com/security/CVE-2024-36945
report https://ubuntu.com/security/CVE-2024-42230
report https://ubuntu.com/security/CVE-2024-46753
report https://ubuntu.com/security/CVE-2024-46812
report https://ubuntu.com/security/CVE-2024-46821
report https://ubuntu.com/security/CVE-2024-53144
report https://ubuntu.com/security/CVE-2024-56664
report https://ubuntu.com/security/CVE-2024-58093
report https://ubuntu.com/security/CVE-2025-21941
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-21962
report https://ubuntu.com/security/CVE-2025-21963
report https://ubuntu.com/security/CVE-2025-21964
report https://ubuntu.com/security/CVE-2025-21968
report https://ubuntu.com/security/CVE-2025-21970
report https://ubuntu.com/security/CVE-2025-21975
report https://ubuntu.com/security/CVE-2025-21981
report https://ubuntu.com/security/CVE-2025-21991
report https://ubuntu.com/security/CVE-2025-21992
report https://ubuntu.com/security/CVE-2025-21994
report https://ubuntu.com/security/CVE-2025-21996
report https://ubuntu.com/security/CVE-2025-21999
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-22008
report https://ubuntu.com/security/CVE-2025-22010
report https://ubuntu.com/security/CVE-2025-22014
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-22025
report https://ubuntu.com/security/CVE-2025-22035
report https://ubuntu.com/security/CVE-2025-22044
report https://ubuntu.com/security/CVE-2025-22045
report https://ubuntu.com/security/CVE-2025-22050
report https://ubuntu.com/security/CVE-2025-22054
report https://ubuntu.com/security/CVE-2025-22055
report https://ubuntu.com/security/CVE-2025-22056
report https://ubuntu.com/security/CVE-2025-22060
report https://ubuntu.com/security/CVE-2025-22063
report https://ubuntu.com/security/CVE-2025-22066
report https://ubuntu.com/security/CVE-2025-22071
report https://ubuntu.com/security/CVE-2025-22073
report https://ubuntu.com/security/CVE-2025-22075
report https://ubuntu.com/security/CVE-2025-22079
report https://ubuntu.com/security/CVE-2025-22081
report https://ubuntu.com/security/CVE-2025-22086
report https://ubuntu.com/security/CVE-2025-22089
report https://ubuntu.com/security/CVE-2025-22097
report https://ubuntu.com/security/CVE-2025-23136
report https://ubuntu.com/security/CVE-2025-23138
report https://ubuntu.com/security/CVE-2025-37785
report https://ubuntu.com/security/CVE-2025-37889
report https://ubuntu.com/security/CVE-2025-37937
report https://ubuntu.com/security/CVE-2025-38152
report https://ubuntu.com/security/CVE-2025-38575
report https://ubuntu.com/security/CVE-2025-38637
report https://ubuntu.com/security/CVE-2025-39728
report https://ubuntu.com/security/CVE-2025-39735