CVE-2022-23960 medium CVSS 5.6

Vulnerability in :linux_kernel: (CVE-2022-23960)

Summary

Vulnerability in :linux_kernel: (CVE-2022-23960). Confidential information can be exposed externally. Mitigation: upgrade to :2022-12-05 or later.

Original description

The description as published by the source.

In specific ARM processors, there is a possible side-channel information leak due to a hardware flaw. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

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-23960 has been found in :linux_kernel:.
Confidential information can be exposed externally. CVSS score: 5.6/10.
What to do: upgrade :linux_kernel: to :2022-12-05 or later.
If unsure, ask your IT team or search ":linux_kernel: CVE-2022-23960" on the vendor's site.

CVE-2022-23960 (:linux_kernel:) — CVSS v3 5.6
Attack vector: local / no user interaction
Patched: :2022-12-05 — 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_kernel:.

📍 Affected scope

Check the vendor advisory for the affected versions of :linux_kernel:.

🔥 Severity

Severity: Medium (CVSS 5.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to :2022-12-05.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで :linux_kernel: を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade :linux_kernel: to :2022-12-05
```
ステージング環境で :2022-12-05 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Android :linux_kernel:

[{"type":"ECOSYSTEM","events":[{"introduced":":0"},{"fixed":":2022-12-05"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2022-23960 linux Fixed in: 5.10.106-1
Ubuntu UBUNTU-CVE-2022-23960 linux-azure Fixed in: 4.15.0-1142.156~14.04.1