← Back
USN-7719-1
Vulnerability in linux-raspi-realtime (USN-7719-1)
Summary
vulnerability in linux-raspi-realtime (USN-7719-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `6.8.0-2028.29` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-7719-1** has been found in linux-raspi-realtime.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade linux-raspi-realtime to **6.8.0-2028.29** or later.
If unsure, ask your IT team or search "linux-raspi-realtime USN-7719-1" on the vendor's site.
USN-7719-1 (linux-raspi-realtime) —
Patched: `6.8.0-2028.29` — 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-raspi-realtime.
📍 Affected scope
linux-raspi-realtime — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **6.8.0-2028.29**.
🛡️ 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-raspi-realtime' .` 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-raspi-realtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-raspi-realtime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-raspi-realtime to 6.8.0-2028.29ステージング環境で 6.8.0-2028.29 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:Realtime:24.04:LTS
linux-raspi-realtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2028.29"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-7719-1
- report https://ubuntu.com/security/CVE-2024-58088
- report https://ubuntu.com/security/CVE-2025-21706
- report https://ubuntu.com/security/CVE-2025-21746
- report https://ubuntu.com/security/CVE-2025-21773
- report https://ubuntu.com/security/CVE-2025-21775
- report https://ubuntu.com/security/CVE-2025-21783
- report https://ubuntu.com/security/CVE-2025-21784
- report https://ubuntu.com/security/CVE-2025-21790
- report https://ubuntu.com/security/CVE-2025-21793
- report https://ubuntu.com/security/CVE-2025-21836
- report https://ubuntu.com/security/CVE-2025-21847
- report https://ubuntu.com/security/CVE-2025-21854
- report https://ubuntu.com/security/CVE-2025-21856
- report https://ubuntu.com/security/CVE-2025-21864
- report https://ubuntu.com/security/CVE-2025-21867
- report https://ubuntu.com/security/CVE-2025-21868
- report https://ubuntu.com/security/CVE-2025-21869
- report https://ubuntu.com/security/CVE-2025-21870
- report https://ubuntu.com/security/CVE-2024-52559
- report https://ubuntu.com/security/CVE-2024-54456
- report https://ubuntu.com/security/CVE-2024-54458
- report https://ubuntu.com/security/CVE-2024-57834
- report https://ubuntu.com/security/CVE-2024-57977
- report https://ubuntu.com/security/CVE-2024-58020
- report https://ubuntu.com/security/CVE-2024-58086
- report https://ubuntu.com/security/CVE-2024-58093
- report https://ubuntu.com/security/CVE-2025-21704
- report https://ubuntu.com/security/CVE-2025-21712
- report https://ubuntu.com/security/CVE-2025-21758
- report https://ubuntu.com/security/CVE-2025-21759
- report https://ubuntu.com/security/CVE-2025-21760
- report https://ubuntu.com/security/CVE-2025-21761
- report https://ubuntu.com/security/CVE-2025-21762
- report https://ubuntu.com/security/CVE-2025-21763
- report https://ubuntu.com/security/CVE-2025-21764
- report https://ubuntu.com/security/CVE-2025-21765
- report https://ubuntu.com/security/CVE-2025-21766
- report https://ubuntu.com/security/CVE-2025-21767
- report https://ubuntu.com/security/CVE-2025-21768
- report https://ubuntu.com/security/CVE-2025-21772
- report https://ubuntu.com/security/CVE-2025-21776
- report https://ubuntu.com/security/CVE-2025-21779
- report https://ubuntu.com/security/CVE-2025-21780
- report https://ubuntu.com/security/CVE-2025-21781
- report https://ubuntu.com/security/CVE-2025-21782
- report https://ubuntu.com/security/CVE-2025-21785
- report https://ubuntu.com/security/CVE-2025-21786
- report https://ubuntu.com/security/CVE-2025-21787
- report https://ubuntu.com/security/CVE-2025-21791
- report https://ubuntu.com/security/CVE-2025-21792
- report https://ubuntu.com/security/CVE-2025-21795
- report https://ubuntu.com/security/CVE-2025-21796
- report https://ubuntu.com/security/CVE-2025-21821
- report https://ubuntu.com/security/CVE-2025-21823
- report https://ubuntu.com/security/CVE-2025-21835
- report https://ubuntu.com/security/CVE-2025-21838
- report https://ubuntu.com/security/CVE-2025-21839
- report https://ubuntu.com/security/CVE-2025-21844
- report https://ubuntu.com/security/CVE-2025-21846
- report https://ubuntu.com/security/CVE-2025-21848
- report https://ubuntu.com/security/CVE-2025-21853
- report https://ubuntu.com/security/CVE-2025-21855
- report https://ubuntu.com/security/CVE-2025-21857
- report https://ubuntu.com/security/CVE-2025-21858
- report https://ubuntu.com/security/CVE-2025-21859
- report https://ubuntu.com/security/CVE-2025-21861
- report https://ubuntu.com/security/CVE-2025-21862
- report https://ubuntu.com/security/CVE-2025-21863
- report https://ubuntu.com/security/CVE-2025-21866
- report https://ubuntu.com/security/CVE-2025-21871
- report https://ubuntu.com/security/CVE-2025-37797
- report https://ubuntu.com/security/CVE-2025-38083