dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49451

MEDIUM · 5.5 CVSS v3.1 Published 2025-02-26
Fix available
A fix is available. Upgrade to 4.19.247 / 5.4.198 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scmi: Fix list protocols enumeration in the base protocol While enumerating protocols implemented by the SCMI platform using BASE_DISCOVER_LIST_PROTOCOLS, the number of returned protocols is currently validated in an improper way since the check employs a sum between unsigned integers that could overflow and cause the check itself to be silently bypassed if the returned value 'loop_num_ret' is big enough. Fix the validation avoiding the addition.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.17, < 4.19.247>= 4.20, < 5.4.198>= 5.5, < 5.10.121>= 5.11, < 5.15.46>= 5.16, < 5.17.14>= 5.18, < 5.18.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.19.247 / 5.4.198 / 5.10.121 or later
Fixed in 4.19.2475.4.1985.10.121
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 4.19.247+ / 5.4.198+ / 5.10.121+ / 5.15.46+ (depending on your current branch)

  1. Identify the current kernel version using 'uname -r'
  2. Determine which stable kernel branch your version belongs to based on the affected version ranges
  3. Upgrade to a fixed kernel version: for 4.19.x branch upgrade to >= 4.19.247, for 5.4.x branch upgrade to >= 5.4.198, for 5.10.x branch upgrade to >= 5.10.121, or for 5.15.x branch upgrade to >= 5.15.46
  4. Use your distribution's package manager to install the updated kernel (e.g., 'apt-get update && apt-get install linux-image-<version>' for Debian/Ubuntu, 'yum update kernel' for RHEL/CentOS, or 'pacman -Syu' for Arch)
  5. Reboot the system to load the patched kernel
  6. Verify the new kernel version is running with 'uname -r'
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom modules or specific hardware drivers; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-49451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-49451 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data