This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2022-48735 →

UBUNTU-CVE-2022-48735

Vulnerability in linux-hwe-edge (UBUNTU-CVE-2022-48735)

Summary

Vulnerability in linux-hwe-edge (UBUNTU-CVE-2022-48735). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.15.0-1008.11~20.04.1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix UAF of leds class devs at unbinding The LED class devices that are created by HD-audio codec drivers are registered via devm_led_classdev_register() and associated with the HD-audio codec device. Unfortunately, it turned out that the devres release doesn't work for this case; namely, since the codec resource release happens before the devm call chain, it triggers a NULL dereference or a UAF for a stale set_brightness_delay callback. For fixing the bug, this patch changes the LED class device register and unregister in a manual manner without devres, keeping the instances in hda_gen_spec.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 UBUNTU-CVE-2022-48735 has been found in linux-hwe-edge.
Successful exploitation can lead to full system takeover.
What to do: upgrade linux-hwe-edge to 5.15.0-1008.11~20.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2022-48735" on the vendor's site.

UBUNTU-CVE-2022-48735 (linux-hwe-edge)
Attack vector: local / no user interaction
Patched: 5.15.0-1008.11~20.04.1 — 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-hwe-edge.

📍 Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 5.15.0-1008.11~20.04.1.

🛡️ 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-hwe-edge' . 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

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