LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48657: arm64: topology: fix possible overflow in amu_fie_setup()

In the Linux kernel, the following vulnerability has been resolved: arm64: topology: fix possible overflow in amu_fie_setup() cpufreq_get_hw_max_freq() returns max frequency in kHz as *unsigned int*, while freq_inv_set_max_ratio() gets passed this frequency in Hz as 'u64'. Multiplying max frequency by 1000 can potentially result in overflow -- multiplying by 1000ULL instead should avoid that... Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel arm64 arithmetic bug in CPU frequency topology handling. A frequency value could overflow when converted from kHz to Hz, potentially causing incorrect internal calculations. The source does not provide impact details, a CVSS score, or evidence of exploitation.

Executive priority

Treat as a kernel maintenance item unless vendor guidance raises severity. There is no source-backed evidence of exploitation, but kernel arithmetic flaws should still be handled through normal patch governance.

Technical view

In amu_fie_setup(), cpufreq_get_hw_max_freq() returns an unsigned int in kHz. The vulnerable logic multiplied it by 1000 before passing a u64 Hz value to freq_inv_set_max_ratio(), creating a possible overflow. The fix uses 1000ULL to force 64-bit arithmetic.

Likely exposure

Exposure appears limited to Linux kernel deployments on arm64 where the affected topology, AMU FIE, and cpufreq code path is present. The provided version data is not sufficient to reliably map all affected distribution kernels.

Exploitation context

The bundle states this was found by static analysis and is not listed as CISA KEV. No cited source claims active exploitation, public exploit availability, or a practical attack path.

Researcher notes

The available record names the vulnerable function and integer promotion issue, but does not document reachability, security impact, or affected distribution builds. Avoid assuming exploitability without vendor analysis or kernel-specific validation.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2022-48657 coverage.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize arm64 systems using CPU frequency scaling or AMU-related topology features.
  • Track distribution backports instead of relying only on upstream version numbers.

Validation and detection

  • Inventory arm64 Linux systems and their running kernel versions.
  • Compare vendor kernel packages against CVE-2022-48657 advisories.
  • Confirm the relevant stable fix commit is present or backported.
  • Review kernel update records for the referenced topology overflow fix.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2022-48657 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6, cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6, cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6, cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6unaffected
LinuxLinux5.7, 0, 5.10.150, 5.15.71, 5.19.12, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.