CVE-2022-49750: cpufreq: CPPC: Add u64 casts to avoid overflowing
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: CPPC: Add u64 casts to avoid overflowing
The fields of the _CPC object are unsigned 32-bits values.
To avoid overflows while using _CPC's values, add 'u64' casts.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49750 is a Linux kernel availability issue in CPU frequency handling. A local, low-privileged user could potentially trigger a high availability impact. The sources do not show data theft, privilege escalation, remote attack, or active exploitation.
Executive priority
Treat as a moderate operational reliability issue. It is not shown as remotely exploitable or actively exploited, but kernel availability impact can matter on shared servers, workstations, and multi-tenant environments.
Technical view
The Linux cpufreq CPPC code used unsigned 32-bit _CPC object values in a way that could overflow. Kernel stable commits resolve it by adding u64 casts. CVSS 3.1 is 5.5: local access, low complexity, low privileges, no user interaction, availability impact only.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions identified in the CVE data, including 5.19 through fixed stable releases 6.1.9 and 6.2. Systems using CPPC/_CPC CPU performance data are the relevant technical area. The sources do not map exposure to specific Linux distributions.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The CVSS vector indicates local exploitation with low privileges and no user interaction. Public sources here do not provide an exploit narrative or observed attacks.
Researcher notes
Primary evidence is the CVE record and two Linux stable commits. The root cause is integer overflow avoidance in cpufreq CPPC calculations involving ACPI _CPC values. Distro-specific affected package ranges are not provided in this source bundle.
Mitigation direction
Upgrade to a kernel version containing the referenced stable fixes.
Check Linux distribution advisories for packaged kernel backports.
Prioritize systems where local users or workloads are less trusted.
Track vendor guidance if exact kernel lineage is unclear.
Validation and detection
Inventory Linux kernel versions across servers and endpoints.
Compare running kernels against affected and fixed versions in the CVE record.
Review distribution changelogs for the referenced kernel stable commits.
Confirm remediation through vulnerability scanner or kernel package metadata.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.