← Retour
USN-7383-2
Vulnérabilité dans linux-realtime (USN-7383-2)
Résumé
vulnérabilité dans linux-realtime (USN-7383-2). Risque d'opérations non autorisées ou de divulgation. Atténuation : mise à jour vers `6.8.1-1018.19` ou plus.
Résumé IA snake-internal / snake-material-v2
Une vulnérabilité référencée **USN-7383-2** a été découverte dans linux-realtime.
Risque d'opérations non autorisées ou de divulgation. Score CVSS : ?/10.
Action : mettez à jour linux-realtime vers **6.8.1-1018.19** ou supérieur.
En cas de doute, contactez votre service informatique ou cherchez « linux-realtime USN-7383-2 » sur le site de l'éditeur.
USN-7383-2 (linux-realtime) —
Correctif : `6.8.1-1018.19` — 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-realtime.
📍 Périmètre concerné
linux-realtime — .
🔥 Gravité
Gravité : ?. Risque d'opérations non autorisées ou de divulgation
🔧 Comment corriger
Mettre à jour vers **6.8.1-1018.19**.
🛡️ 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
-
1Identify exposure identify
grep -r 'linux-realtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-realtime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-realtime to 6.8.1-1018.19ステージング環境で 6.8.1-1018.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Paquets affectés
Ubuntu:Pro:Realtime:24.04:LTS
linux-realtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1018.19"}]}]
Références
- advisory https://ubuntu.com/security/notices/USN-7383-2
- report https://ubuntu.com/security/CVE-2024-47711
- report https://ubuntu.com/security/CVE-2024-49865
- report https://ubuntu.com/security/CVE-2024-49972
- report https://ubuntu.com/security/CVE-2024-50020
- report https://ubuntu.com/security/CVE-2024-50021
- report https://ubuntu.com/security/CVE-2024-50022
- report https://ubuntu.com/security/CVE-2024-50023
- report https://ubuntu.com/security/CVE-2024-50025
- report https://ubuntu.com/security/CVE-2024-50026
- report https://ubuntu.com/security/CVE-2024-50027
- report https://ubuntu.com/security/CVE-2024-50029
- report https://ubuntu.com/security/CVE-2024-50030
- report https://ubuntu.com/security/CVE-2024-50032
- report https://ubuntu.com/security/CVE-2024-50042
- report https://ubuntu.com/security/CVE-2024-50064
- report https://ubuntu.com/security/CVE-2024-50065
- report https://ubuntu.com/security/CVE-2024-50066
- report https://ubuntu.com/security/CVE-2024-50068
- report https://ubuntu.com/security/CVE-2024-50069
- report https://ubuntu.com/security/CVE-2024-50070
- report https://ubuntu.com/security/CVE-2024-50072
- report https://ubuntu.com/security/CVE-2024-50074
- report https://ubuntu.com/security/CVE-2024-50076
- report https://ubuntu.com/security/CVE-2024-50077
- report https://ubuntu.com/security/CVE-2024-50078
- report https://ubuntu.com/security/CVE-2024-50080
- report https://ubuntu.com/security/CVE-2024-50084
- report https://ubuntu.com/security/CVE-2024-50085
- report https://ubuntu.com/security/CVE-2024-50087
- report https://ubuntu.com/security/CVE-2024-50088
- report https://ubuntu.com/security/CVE-2024-50090
- report https://ubuntu.com/security/CVE-2024-50101
- report https://ubuntu.com/security/CVE-2024-50193
- report https://ubuntu.com/security/CVE-2024-50197
- report https://ubuntu.com/security/CVE-2024-50200
- report https://ubuntu.com/security/CVE-2024-53170
- report https://ubuntu.com/security/CVE-2024-56582
- report https://ubuntu.com/security/CVE-2024-56663
- report https://ubuntu.com/security/CVE-2024-47726
- report https://ubuntu.com/security/CVE-2024-49893
- report https://ubuntu.com/security/CVE-2024-49914
- report https://ubuntu.com/security/CVE-2024-49920
- report https://ubuntu.com/security/CVE-2024-49921
- report https://ubuntu.com/security/CVE-2024-49968
- report https://ubuntu.com/security/CVE-2024-50009
- report https://ubuntu.com/security/CVE-2024-50019
- report https://ubuntu.com/security/CVE-2024-50024
- report https://ubuntu.com/security/CVE-2024-50028
- report https://ubuntu.com/security/CVE-2024-50031
- report https://ubuntu.com/security/CVE-2024-50033
- report https://ubuntu.com/security/CVE-2024-50035
- report https://ubuntu.com/security/CVE-2024-50036
- report https://ubuntu.com/security/CVE-2024-50038
- report https://ubuntu.com/security/CVE-2024-50039
- report https://ubuntu.com/security/CVE-2024-50040
- report https://ubuntu.com/security/CVE-2024-50041
- report https://ubuntu.com/security/CVE-2024-50044
- report https://ubuntu.com/security/CVE-2024-50045
- report https://ubuntu.com/security/CVE-2024-50046
- report https://ubuntu.com/security/CVE-2024-50047
- report https://ubuntu.com/security/CVE-2024-50048
- report https://ubuntu.com/security/CVE-2024-50049
- report https://ubuntu.com/security/CVE-2024-50055
- report https://ubuntu.com/security/CVE-2024-50056
- report https://ubuntu.com/security/CVE-2024-50057
- report https://ubuntu.com/security/CVE-2024-50058
- report https://ubuntu.com/security/CVE-2024-50059
- report https://ubuntu.com/security/CVE-2024-50060
- report https://ubuntu.com/security/CVE-2024-50061
- report https://ubuntu.com/security/CVE-2024-50062
- report https://ubuntu.com/security/CVE-2024-50063
- report https://ubuntu.com/security/CVE-2024-50073
- report https://ubuntu.com/security/CVE-2024-50075
- report https://ubuntu.com/security/CVE-2024-50082
- report https://ubuntu.com/security/CVE-2024-50083
- report https://ubuntu.com/security/CVE-2024-50086
- report https://ubuntu.com/security/CVE-2024-50093
- report https://ubuntu.com/security/CVE-2024-50095
- report https://ubuntu.com/security/CVE-2024-50096
- report https://ubuntu.com/security/CVE-2024-50098
- report https://ubuntu.com/security/CVE-2024-50099
- report https://ubuntu.com/security/CVE-2024-50117
- report https://ubuntu.com/security/CVE-2024-50134
- report https://ubuntu.com/security/CVE-2024-50148
- report https://ubuntu.com/security/CVE-2024-50171
- report https://ubuntu.com/security/CVE-2024-50180
- report https://ubuntu.com/security/CVE-2024-50182
- report https://ubuntu.com/security/CVE-2024-50183
- report https://ubuntu.com/security/CVE-2024-50184
- report https://ubuntu.com/security/CVE-2024-50185
- report https://ubuntu.com/security/CVE-2024-50186
- report https://ubuntu.com/security/CVE-2024-50187
- report https://ubuntu.com/security/CVE-2024-50188
- report https://ubuntu.com/security/CVE-2024-50189
- report https://ubuntu.com/security/CVE-2024-50191
- report https://ubuntu.com/security/CVE-2024-50192
- report https://ubuntu.com/security/CVE-2024-50194
- report https://ubuntu.com/security/CVE-2024-50195
- report https://ubuntu.com/security/CVE-2024-50196
- report https://ubuntu.com/security/CVE-2024-50198
- report https://ubuntu.com/security/CVE-2024-50199
- report https://ubuntu.com/security/CVE-2024-50201
- report https://ubuntu.com/security/CVE-2024-50202
- report https://ubuntu.com/security/CVE-2024-50229
- report https://ubuntu.com/security/CVE-2024-50233
- report https://ubuntu.com/security/CVE-2024-53156
- report https://ubuntu.com/security/CVE-2024-53165
- report https://ubuntu.com/security/CVE-2024-56614