CVE-2022-49748: perf/x86/amd: fix potential integer overflow on shift of a int
In the Linux kernel, the following vulnerability has been resolved:
perf/x86/amd: fix potential integer overflow on shift of a int
The left shift of int 32 bit integer constant 1 is evaluated using 32 bit
arithmetic and then passed as a 64 bit function argument. In the case where
i is 32 or more this can lead to an overflow. Avoid this by shifting
using the BIT_ULL macro instead.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49748 is a Linux kernel bug in AMD x86 perf handling. A local low-privileged user could potentially trigger a denial of service. The sourced CVSS score is medium, with availability impact only and no confidentiality or integrity impact stated.
Executive priority
Treat as a moderate operational availability risk. It is most urgent for shared Linux environments where local users or workloads are less trusted. Patch through normal kernel maintenance unless local denial-of-service risk is business-critical.
Technical view
The issue is an integer overflow from shifting a 32-bit int constant before passing it as a 64-bit argument. When the shift index is 32 or higher, overflow can occur. The kernel fix uses BIT_ULL for 64-bit-safe shifting in perf/x86/amd code.
Likely exposure
Exposure is local, not network-facing. Linux systems running affected kernel versions in the AMD x86 perf code path are the relevant population, especially multi-user hosts, shared compute, and systems allowing low-privileged local code execution.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. CVSS indicates local access, low complexity, low privileges, no user interaction, and high availability impact.
Researcher notes
The affected data lists Linux kernel versions and commit identifiers, but distribution backport status is not included. Validate impact against downstream vendor kernels rather than relying only on upstream version numbers.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Prioritize shared or multi-user Linux systems for remediation.
Check your Linux distribution advisories for backported kernel fixes.
Avoid assuming product impact beyond the Linux kernel data provided.
Validation and detection
Inventory Linux kernel versions across affected fleets.
Compare running kernels against vendor advisories and referenced stable commits.
Confirm whether systems use AMD x86 perf-related kernel code paths.
Track remediation through package version or kernel build evidence.
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.