vciy

CVE-2022-50634

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

power: supply: cw2015: Fix potential null-ptr-deref in cw_bat_probe()

CVE-2022-506342 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Hindsight · the state

0.00197EPSSNOT IN KEVas of 2026-10-18
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defensefix not stated as a versionreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-12-09, 269 days at 0.00, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Linux? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch Linux

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inThe CVE record names a fix, but not as a version that can be installed. What it holds is a source commit, a placeholder, or a version the record itself lists as affected.receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00197 · top 91% of all CVEsreceipt
Assigned byLinuxreceipt
Recorded changes13 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productLinuxreceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

In the Linux kernel, the following vulnerability has been resolved: power: supply: cw2015: Fix potential null-ptr-deref in cw_bat_probe() cw_bat_probe() calls create_singlethread_workqueue() and not checked the ret value, which may return NULL. And a null-ptr-deref may happen: cw_bat_probe() create_singlethread_workqueue() # failed, cw_bat->wq is NULL queue_delayed_work() queue_delayed_work_on() __queue_delayed_work() # warning here, but continue __queue_work() # access wq->flags, null-ptr-deref Check the ret value and return -ENOMEM if it is NULL. receipt

check it yourself git.kernel.org git.kernel.org git.kernel.org receipt

Movement the material steps

9 Dec 20250.00017
15 Jun 20260.00166 · scoring model v2026.06.15
4 Sep 20260.00197
Show all 13 observations
9 Dec 20250.00017
15 Dec 20250.00022
10 Jan 20260.00024
15 Feb 20260.00025
10 Apr 20260.00032
7 May 20260.00021
8 May 20260.0002
19 May 20260.00024
15 Jun 20260.00166
8 Jul 20260.00172
28 Jul 20260.00176
6 Aug 20260.00193
4 Sep 20260.00197

13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00197Published2025-12-09Index as of2026-09-04

The record had been public for 8 months when this index was last written.

Published 2025-12-09 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2022-50634.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.