# power: supply: core: Fix boundary conditions in interpolation

CVE record · `CVE-2022-49612`

- **Identifiers:** `CVE-2022-49612`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 26 Feb 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 26 Feb 2025, 02:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `a4585ba2050f460f749bbaf2b67bd56c41e30283 to before a762cee5d933fe4e2e1b773d60fc74fb8248d8c4` (git)
  - affected: `a4585ba2050f460f749bbaf2b67bd56c41e30283 to before 093d27bb6f2d1963f927ef59c9a2d37059175426` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.17`
  - unaffected: `before 5.17` (semver)
  - unaffected: `5.18.13 to 5.18.*, inclusive` (semver)
  - unaffected: `5.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's power supply core is vulnerable in the 5.17 series, where interpolation in the battery voltage-to-capacity and temperature-to-resistance lookups mishandles boundary conditions. The source gives few details on what an attacker needs, but the flaw can cause an out-of-bounds read. Upgrade to Linux 5.18.13 or later, or to 5.19 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 26 Feb 2025, 02:23 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49612)
- 26 Feb 2025, 07:01 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49612)

## Sources

- [CVE List: CVE-2022-49612](https://www.cve.org/CVERecord?id=CVE-2022-49612)
- [NVD: CVE-2022-49612](https://nvd.nist.gov/vuln/detail/CVE-2022-49612)

### References from the CNA

- <https://git.kernel.org/stable/c/a762cee5d933fe4e2e1b773d60fc74fb8248d8c4>
- <https://git.kernel.org/stable/c/093d27bb6f2d1963f927ef59c9a2d37059175426>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49612>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49612/>. Everything for agents: <https://agentprime.io/llms.txt>.
