Vulnerability in linux (DEBIAN-CVE-2026-45869)

Summary

Vulnerability in linux (DEBIAN-CVE-2026-45869). Risk of unauthorized operations or information disclosure. Exploitable via power_supply. Mitigation: upgrade to 5.10.257-1 or later.

Original description

The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: power: supply: wm97xx: Fix NULL pointer dereference in power_supply_changed() In probe(), request_irq() is called before allocating/registering a power_supply handle. If an interrupt is fired between the call to request_irq() and power_supply_register(), the power_supply handle will be used uninitialized in power_supply_changed() in wm97xx_bat_update() (triggered from the interrupt handler). This will lead to a NULL pointer dereference since Fix this racy NULL pointer dereference by making sure the IRQ is requested after the registration of the power_supply handle. Since the IRQ is the last thing requests in the probe() now, remove the error path for freeing it. Instead add one for unregistering the power_supply handle when IRQ request fails.

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 DEBIAN-CVE-2026-45869 has been found in linux.
Attackers can target a specific entry point like power_supply over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux to 5.10.257-1 or later.
If unsure, ask your IT team or search "linux DEBIAN-CVE-2026-45869" on the vendor's site.

DEBIAN-CVE-2026-45869 (linux)
Attack surface: power_supply / NULL
Patched: 5.10.257-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. Attackers reach the vulnerable code path via power_supply.

📍 Affected scope

Check the vendor advisory for the affected versions of linux. Attack surface: power_supply / NULL.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

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

Affected packages

Debian:11 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.257-1"}]}]

Debian:12 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.170-1"}]}]

Debian:13 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.85-1"}]}]

Debian:14 linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.14-1"}]}]

References

advisory security-tracker.debian.org