Vulnerability in Kernel (CVE-2022-50412)

Summary

Vulnerability in Kernel (CVE-2022-50412). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.10.234, 5.15.75, 5.19.17, 6.0.3 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved:

drm: bridge: adv7511: unregister cec i2c device after cec adapter

cec_unregister_adapter() assumes that the underlying adapter ops are
callable. For example, if the CEC adapter currently has a valid physical
address, then the unregistration procedure will invalidate the physical
address by setting it to f.f.f.f. Whence the following kernel oops
observed after removing the adv7511 module:

Unable to handle kernel execution of user memory at virtual address 0000000000000000
Internal error: Oops: 86000004 [#1] PREEMPT_RT SMP
Call trace:
 0x0
 adv7511_cec_adap_log_addr+0x1ac/0x1c8 [adv7511]
 cec_adap_unconfigure+0x44/0x90 [cec]
 __cec_s_phys_addr.part.0+0x68/0x230 [cec]
 __cec_s_phys_addr+0x40/0x50 [cec]
 cec_unregister_adapter+0xb4/0x118 [cec]
 adv7511_remove+0x60/0x90 [adv7511]
 i2c_device_remove+0x34/0xe0
 device_release_driver_internal+0x114/0x1f0
 driver_detach+0x54/0xe0
 bus_remove_driver+0x60/0xd8
 driver_unregister+0x34/0x60
 i2c_del_driver+0x2c/0x68
 adv7511_exit+0x1c/0x67c [adv7511]
 __arm64_sys_delete_module+0x154/0x288
 invoke_syscall+0x48/0x100
 el0_svc_common.constprop.0+0x48/0xe8
 do_el0_svc+0x28/0x88
 el0_svc+0x1c/0x50
 el0t_64_sync_handler+0xa8/0xb0
 el0t_64_sync+0x15c/0x160
Code: bad PC value
---[ end trace 0000000000000000 ]---

Protect against this scenario by unregistering i2c_cec after
u…

Source: OSV.dev (Open Source Vulnerabilities) NVD 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 CVE-2022-50412 has been found in Kernel.
Successful exploitation can lead to full system takeover.
What to do: upgrade Kernel to 5.10.234, 5.15.75, 5.19.17, 6.0.3 or later.
If unsure, ask your IT team or search "Kernel CVE-2022-50412" on the vendor's site.

CVE-2022-50412 (Kernel)
Attack vector: local / no user interaction
Patched: 5.10.234, 5.15.75, 5.19.17, 6.0.3 — 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 Kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel.

🔥 Severity

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

🔧 How to fix

Update to 5.10.234, 5.15.75, 5.19.17, 6.0.3.

🛡️ 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 '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

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

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"4.15.0"},{"fixed":"5.10.234"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.75"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"5.19.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.20.0"},{"fixed":"6.0.3"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2022-50412 linux Fixed in: 5.10.234-1
Ubuntu UBUNTU-CVE-2022-50412 linux-azure