Vulnérabilité dans linux-intel-iotg (USN-6795-1)

Résumé

vulnérabilité dans linux-intel-iotg (USN-6795-1). Risque d'opérations non autorisées ou de divulgation. Atténuation : mise à jour vers `5.15.0-1057.63` ou plus.

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

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

USN-6795-1 (linux-intel-iotg) — Correctif : `5.15.0-1057.63` — 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-intel-iotg.

📍 Périmètre concerné

linux-intel-iotg — .

🔥 Gravité

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

🔧 Comment corriger

Mettre à jour vers **5.15.0-1057.63**.

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

Paquets affectés

Ubuntu:22.04:LTS linux-intel-iotg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.63"}]}]

Références

advisory https://ubuntu.com/security/notices/USN-6795-1
report https://ubuntu.com/security/CVE-2024-26720
report https://ubuntu.com/security/CVE-2024-26722
report https://ubuntu.com/security/CVE-2024-26910
report https://ubuntu.com/security/CVE-2024-26916
report https://ubuntu.com/security/CVE-2023-47233
report https://ubuntu.com/security/CVE-2023-52435
report https://ubuntu.com/security/CVE-2023-52486
report https://ubuntu.com/security/CVE-2023-52489
report https://ubuntu.com/security/CVE-2023-52491
report https://ubuntu.com/security/CVE-2023-52492
report https://ubuntu.com/security/CVE-2023-52493
report https://ubuntu.com/security/CVE-2023-52494
report https://ubuntu.com/security/CVE-2023-52498
report https://ubuntu.com/security/CVE-2023-52530
report https://ubuntu.com/security/CVE-2023-52583
report https://ubuntu.com/security/CVE-2023-52587
report https://ubuntu.com/security/CVE-2023-52588
report https://ubuntu.com/security/CVE-2023-52594
report https://ubuntu.com/security/CVE-2023-52595
report https://ubuntu.com/security/CVE-2023-52597
report https://ubuntu.com/security/CVE-2023-52598
report https://ubuntu.com/security/CVE-2023-52599
report https://ubuntu.com/security/CVE-2023-52601
report https://ubuntu.com/security/CVE-2023-52602
report https://ubuntu.com/security/CVE-2023-52604
report https://ubuntu.com/security/CVE-2023-52606
report https://ubuntu.com/security/CVE-2023-52607
report https://ubuntu.com/security/CVE-2023-52608
report https://ubuntu.com/security/CVE-2023-52614
report https://ubuntu.com/security/CVE-2023-52615
report https://ubuntu.com/security/CVE-2023-52616
report https://ubuntu.com/security/CVE-2023-52617
report https://ubuntu.com/security/CVE-2023-52618
report https://ubuntu.com/security/CVE-2023-52619
report https://ubuntu.com/security/CVE-2023-52622
report https://ubuntu.com/security/CVE-2023-52623
report https://ubuntu.com/security/CVE-2023-52627
report https://ubuntu.com/security/CVE-2023-52631
report https://ubuntu.com/security/CVE-2023-52633
report https://ubuntu.com/security/CVE-2023-52635
report https://ubuntu.com/security/CVE-2023-52637
report https://ubuntu.com/security/CVE-2023-52638
report https://ubuntu.com/security/CVE-2023-52642
report https://ubuntu.com/security/CVE-2023-52643
report https://ubuntu.com/security/CVE-2024-1151
report https://ubuntu.com/security/CVE-2024-2201
report https://ubuntu.com/security/CVE-2024-23849
report https://ubuntu.com/security/CVE-2024-26592
report https://ubuntu.com/security/CVE-2024-26593
report https://ubuntu.com/security/CVE-2024-26594
report https://ubuntu.com/security/CVE-2024-26600
report https://ubuntu.com/security/CVE-2024-26602
report https://ubuntu.com/security/CVE-2024-26606
report https://ubuntu.com/security/CVE-2024-26608
report https://ubuntu.com/security/CVE-2024-26610
report https://ubuntu.com/security/CVE-2024-26614
report https://ubuntu.com/security/CVE-2024-26615
report https://ubuntu.com/security/CVE-2024-26622
report https://ubuntu.com/security/CVE-2024-26625
report https://ubuntu.com/security/CVE-2024-26627
report https://ubuntu.com/security/CVE-2024-26635
report https://ubuntu.com/security/CVE-2024-26636
report https://ubuntu.com/security/CVE-2024-26640
report https://ubuntu.com/security/CVE-2024-26641
report https://ubuntu.com/security/CVE-2024-26644
report https://ubuntu.com/security/CVE-2024-26645
report https://ubuntu.com/security/CVE-2024-26660
report https://ubuntu.com/security/CVE-2024-26663
report https://ubuntu.com/security/CVE-2024-26664
report https://ubuntu.com/security/CVE-2024-26665
report https://ubuntu.com/security/CVE-2024-26668
report https://ubuntu.com/security/CVE-2024-26671
report https://ubuntu.com/security/CVE-2024-26673
report https://ubuntu.com/security/CVE-2024-26675
report https://ubuntu.com/security/CVE-2024-26676
report https://ubuntu.com/security/CVE-2024-26679
report https://ubuntu.com/security/CVE-2024-26684
report https://ubuntu.com/security/CVE-2024-26685
report https://ubuntu.com/security/CVE-2024-26689
report https://ubuntu.com/security/CVE-2024-26695
report https://ubuntu.com/security/CVE-2024-26696
report https://ubuntu.com/security/CVE-2024-26697
report https://ubuntu.com/security/CVE-2024-26698
report https://ubuntu.com/security/CVE-2024-26702
report https://ubuntu.com/security/CVE-2024-26704
report https://ubuntu.com/security/CVE-2024-26707
report https://ubuntu.com/security/CVE-2024-26712
report https://ubuntu.com/security/CVE-2024-26715
report https://ubuntu.com/security/CVE-2024-26717
report https://ubuntu.com/security/CVE-2024-26808
report https://ubuntu.com/security/CVE-2024-26825
report https://ubuntu.com/security/CVE-2024-26826
report https://ubuntu.com/security/CVE-2024-26829
report https://ubuntu.com/security/CVE-2024-26920