Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45869 medium CVSS 5.5

Vulnerability in Linux kernel (CVE-2026-45869)

Summary

Vulnerability in Linux kernel (CVE-2026-45869). Risk of unauthorized operations or information disclosure. Exploitable via power_supply.

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: GitHub Security Advisories (Global) NVD GitHub Advisory

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-2026-45869 has been found in Linux kernel.
Attackers can target a specific entry point like power_supply over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-45869" on the vendor's site.

CVE-2026-45869 (Linux kernel) — CWE-476 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: power_supply / NULL
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 (CWE-476) exists in Linux kernel. Attackers reach the vulnerable code path via power_supply.

📍 Affected scope

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

🔥 Severity

Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.32"},{"fixed":"5.10.252"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.202"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.165"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.128"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.75"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.14"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details