Vulnerability in Kernel (CVE-2022-48701)
Summary
Vulnerability in Kernel (CVE-2022-48701). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9 or later.
Original description
The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usb-audio: Fix an out-of-bounds bug in __snd_usb_parse_audio_interface()
There may be a bad USB audio device with a USB ID of (0x04fa, 0x4201) and
the number of it's interfaces less than 4, an out-of-bounds read bug occurs
when parsing the interface descriptor for this device.
Fix this by checking the number of interfaces.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-48701 has been found in Kernel.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-48701" on the vendor's site.
CVE-2022-48701 (Kernel)
Patched: 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9 — 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.
A vulnerability (unclassified) exists in Kernel.
Check the vendor advisory for the affected versions of Kernel.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Kernel to 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9ステージング環境で 4.9.328, 4.14.293, 4.19.258, 5.4.213, 5.10.143, 5.15.68, 5.19.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2022-48701 linux Fixed in: 5.10.148-1
- Ubuntu UBUNTU-CVE-2022-48701 linux-azure Fixed in: 4.15.0-1158.173~14.04.1
References
- advisory github.com
- advisory nvd.nist.gov
- package git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org