Vulnerability in linux-oem-5.10 (USN-5001-1)

Summary

vulnerability in linux-oem-5.10 (USN-5001-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5.10.0-1033.34` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-5001-1** has been found in linux-oem-5.10. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade linux-oem-5.10 to **5.10.0-1033.34** or later. If unsure, ask your IT team or search "linux-oem-5.10 USN-5001-1" on the vendor's site.

USN-5001-1 (linux-oem-5.10) — Patched: `5.10.0-1033.34` — 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-oem-5.10.

📍 Affected scope

linux-oem-5.10 — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **5.10.0-1033.34**.

🛡️ 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-oem-5.10' .` 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

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

Affected packages

Ubuntu:20.04:LTS linux-oem-5.10

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.0-1033.34"}]}]

References

advisory https://ubuntu.com/security/notices/USN-5001-1
report https://ubuntu.com/security/CVE-2021-3543
report https://ubuntu.com/security/CVE-2021-23134
report https://ubuntu.com/security/CVE-2021-31440
report https://ubuntu.com/security/CVE-2020-24586
report https://ubuntu.com/security/CVE-2020-24587
report https://ubuntu.com/security/CVE-2020-24588
report https://ubuntu.com/security/CVE-2020-26139
report https://ubuntu.com/security/CVE-2020-26141
report https://ubuntu.com/security/CVE-2020-26145
report https://ubuntu.com/security/CVE-2020-26147
report https://ubuntu.com/security/CVE-2021-3506
report https://ubuntu.com/security/CVE-2021-3609
report https://ubuntu.com/security/CVE-2021-23133
report https://ubuntu.com/security/CVE-2021-32399
report https://ubuntu.com/security/CVE-2021-33034