BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49145High confidence

ACPI: CPPC: Avoid out of bounds access when parsing _CPC data

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.28% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-49145 · CSAF 2.0 · revision 76 · interimSUSE Product Security TeamCVE-2022-49145
178 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55080

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/

What

In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-125
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 March 2025, published on 5 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49094 Référence CVE CVE-2022-49097 https://www.cve.org/CVERecord?id=CVE-2022-49097 Référence CVE CVE-2022-49100 https://www.cve.org/CVERecord?id=CVE-2022-49100 Référence CVE CVE-2022-49103 https://www.cve.org/CVERecord?id=CVE-2022-49103 Référence CVE CVE-2022-49107 https://www.cve.org/CVERecord?id=CVE-2022-49107 Référence CVE CVE-2022-49118 https://www.cve.org/CVERecord?id=CVE-2022-49118 Référence CVE CVE-2022-49122 https://www.cve.org/CVERecord?id=CVE-2022-49122 Référence CVE CVE-2022-49130 https://www.cve.org/CVERecord?id=CVE-2022-49130 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49152 https://www.cve.org/CVERecord?id=CVE-2022-49152 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49159 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0529Multiples vulnérabilités dans le noyau Linux de SUSE

ERecord?id=CVE-2021-47670 Référence CVE CVE-2022-3564 https://www.cve.org/CVERecord?id=CVE-2022-3564 Référence CVE CVE-2022-3619 https://www.cve.org/CVERecord?id=CVE-2022-3619 Référence CVE CVE-2022-3640 https://www.cve.org/CVERecord?id=CVE-2022-3640 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2022-48875 https://www.cve.org/CVERecord?id=CVE-2022-48875 Référence CVE CVE-2022-49080 https://www.cve.org/CVERecord?id=CVE-2022-49080 Référence CVE CVE-2022-49110 https://www.cve.org/CVERecord?id=CVE-2022-49110 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49190 https://www.cve.org/CVERecord?id=CVE-2022-49190 Référence CVE CVE-2022-49212 https://www.cve.org/CVERecord?id=CVE-2022-49212 Référence CVE CVE-2022-49216 https://www.cve.org/CVERecord?id=CVE-2022-49216 Référence CVE CVE-2022-49235 https://www.cve.org/CVERecord?id=CVE-2022-49235 Référence CVE CVE-2022-49248 https://www.cve.org/CVERecord?id=CVE-2022-49248 Référence CVE CVE-2022-49253 https://www.cve.org/CVERecord?id=CVE-2022-49253 Référence CVE CVE-2022-49320 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49132 Référence CVE CVE-2022-49133 https://www.cve.org/CVERecord?id=CVE-2022-49133 Référence CVE CVE-2022-49134 https://www.cve.org/CVERecord?id=CVE-2022-49134 Référence CVE CVE-2022-49135 https://www.cve.org/CVERecord?id=CVE-2022-49135 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49138 https://www.cve.org/CVERecord?id=CVE-2022-49138 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49144 https://www.cve.org/CVERecord?id=CVE-2022-49144 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49132 Référence CVE CVE-2022-49133 https://www.cve.org/CVERecord?id=CVE-2022-49133 Référence CVE CVE-2022-49134 https://www.cve.org/CVERecord?id=CVE-2022-49134 Référence CVE CVE-2022-49135 https://www.cve.org/CVERecord?id=CVE-2022-49135 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49138 https://www.cve.org/CVERecord?id=CVE-2022-49138 Référence CVE CVE-2022-49139 https://www.cve.org/CVERecord?id=CVE-2022-49139 Référence CVE CVE-2022-49144 https://www.cve.org/CVERecord?id=CVE-2022-49144 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49122 Référence CVE CVE-2022-49126 https://www.cve.org/CVERecord?id=CVE-2022-49126 Référence CVE CVE-2022-49128 https://www.cve.org/CVERecord?id=CVE-2022-49128 Référence CVE CVE-2022-49129 https://www.cve.org/CVERecord?id=CVE-2022-49129 Référence CVE CVE-2022-49130 https://www.cve.org/CVERecord?id=CVE-2022-49130 Référence CVE CVE-2022-49131 https://www.cve.org/CVERecord?id=CVE-2022-49131 Référence CVE CVE-2022-49132 https://www.cve.org/CVERecord?id=CVE-2022-49132 Référence CVE CVE-2022-49135 https://www.cve.org/CVERecord?id=CVE-2022-49135 Référence CVE CVE-2022-49137 https://www.cve.org/CVERecord?id=CVE-2022-49137 Référence CVE CVE-2022-49145 https://www.cve.org/CVERecord?id=CVE-2022-49145 Référence CVE CVE-2022-49147 https://www.cve.org/CVERecord?id=CVE-2022-49147 Référence CVE CVE-2022-49148 https://www.cve.org/CVERecord?id=CVE-2022-49148 Référence CVE CVE-2022-49151 https://www.cve.org/CVERecord?id=CVE-2022-49151 Référence CVE CVE-2022-49153 https://www.cve.org/CVERecord?id=CVE-2022-49153 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49155 https://www.cve.org/CVERecord?id=CVE-2022-49155 Référence CVE CVE-2022-49156 https://www.cve.org/CVERecord?id=CVE-2022-49156 Référence CVE CVE-2022-49157 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026340Linux の Linux Kernel における境界外読み取りに関する脆弱性

Linux の Linux Kernel には、境界外読み取りに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.4, 4.9.311 ≤ 4.9.*, 4.14.276 ≤ 4.14.*, 4.19.238 ≤ 4.19.*, 5.4.189 ≤ 5.4.*, 5.10.110 ≤ 5.10.*, 5.15.33 ≤ 5.15.*, 5.16.19 ≤ 5.16.*, 5.17.2 ≤ 5.17.*, 5.18 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 11 May 2026, 18:53 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55080
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-55080↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49145 · cve.blacktree.nl