CVE-2022-48657

Unspecified impact via overflowing frequency conversion

Published Apr 28, 2024 · Updated May 11, 2026

Integer overflow in the Linux kernel allows local users to cause unspecified impact during arm64 frequency-invariance setup. The amu_fie_setup path multiplies a hardware maximum reported in kilohertz by 1000 as unsigned-int arithmetic before passing the value as a 64-bit hertz ratio. The path is limited to arm64 systems using AMU-based frequency invariance, and public records describe no demonstrated failure mode beyond the incorrect ratio calculation.

CVSS severity7.8
High
EPSS probability0.25%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Integer overflow in the Linux kernel allows local users to cause unspecified impact during arm64 frequency-invariance setup. The amu_fie_setup path multiplies a hardware maximum reported in kilohertz by 1000 as unsigned-int arithmetic before passing the value as a 64-bit hertz ratio. The path is limited to arm64 systems using AMU-based frequency invariance, and public records describe no demonstrated failure mode beyond the incorrect ratio calculation.

The record

CVE
CVE-2022-48657
Published
Apr 28, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 28, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.7
  2. Affected versionversion=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <3c3edb82d67b2be9231174ac2af4af60d4af7549
  3. Affected versionversion=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <904f881b57360cf85de962d84d8614d94431f60e
  4. Affected versionversion=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <bb6d99e27cbe6b30e4e3bbd32927fd3b0bdec6eb
  5. Affected versionversion=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <d4955c0ad77dbc684fc716387070ac24801b8bca

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.7; version=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <3c3edb82d67b2be9231174ac2af4af60d4af7549; version=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <904f881b57360cf85de962d84d8614d94431f60e; version=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <bb6d99e27cbe6b30e4e3bbd32927fd3b0bdec6eb; version=cd0ed03a8903a0b0c6fc36e32d133d1ddfe70cd6 <d4955c0ad77dbc684fc716387070ac24801b8bca

Published CVSS scores

7.8CanonicalCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo