Skip to content
Noroxi
CVE-2022-49554· NVD / CVE Program· CNA Linux

zsmalloc: fix races between asynchronous zspage free and page migration

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 2505a981114dcb715f8977b8433f7540854851d8, 3674d8a8dadd03a447dd21069d4dacfc3399b63b, 3ec459c8810e658401be428d3168eacfc380bdd0.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 2505a981114dcb715f8977b8433f7540854851d8, 3674d8a8dadd03a447dd21069d4dacfc3399b63b, 3ec459c8810e658401be428d3168eacfc380bdd0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: zsmalloc: fix races between asynchronous zspage free and page migration The asynchronous zspage free worker tries to lock a zspage's entire page list without defending against page migration. Since pages which haven't yet been locked can concurrently migrate off the zspage page list while lock_zspage() churns away, lock_zspage() can suffer from a few different lethal races. It can lock a page which no longer belongs to the zspage and unsafely dereference page_private(), it can unsafely dereference a torn pointer to the next page (since there's a data race), and it can observe a spurious NULL pointer to the next page and thus not lock all of the zspage's pages (since a single page migration will reconstruct the entire page list, and create_page_chain() unconditionally zeroes out each list pointer in the process). Fix the races by using migrate_read_lock() in lock_zspage() to synchronize with page migration.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.7
CNA · Linux
7.8
3.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49554

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.14 and later · before 4.14.282
  • linux linux kernel4.15 and later · before 4.19.246
  • linux linux kernel4.20 and later · before 5.4.197
  • linux linux kernel5.5 and later · before 5.10.120
  • linux linux kernel5.11 and later · before 5.15.45
  • linux linux kernel5.16 and later · before 5.17.13
  • linux linux kernel5.18 and later · before 5.18.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.14affected
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before 3674d8a8dadd03a447dd21069d4dacfc3399b63baffected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before 645996efc2ae391246d595832aaa6f9d3cc338c7affected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before fc658c083904427abbf8f18280d517ee2668677caffected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before fae05b2314b147a78fbed1dc4c645d9a66313758affected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before 3ec459c8810e658401be428d3168eacfc380bdd0affected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before 8ba7b7c1dad1f6503c541778f31b33f7f62eb966affected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before c5402fb5f71f1a725f1e55d9c6799c0c7bec308faffected · git
    • 77ff465799c60294e248000cd22ae8171da3304c and later · before 2505a981114dcb715f8977b8433f7540854851d8affected · git
    • before 4.14not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.2-15.18.2-1

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49178Feb 26, 2025 · memstick/mspro_block: fix handling of read-only devices
    22Monitor
  • ← EarlierCVE-2022-49407Feb 26, 2025 · dlm: fix plock invalid read
    28Monitor
  • Later →CVE-2022-49581Feb 26, 2025 · be2net: Fix buffer overflow in be_get_module_eeprom
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2505a981114dcb715f8977b8433f7540854851d8Vendor (CNA)
Linux Linux3674d8a8dadd03a447dd21069d4dacfc3399b63bVendor (CNA)
Linux Linux3ec459c8810e658401be428d3168eacfc380bdd0Vendor (CNA)
Linux Linux645996efc2ae391246d595832aaa6f9d3cc338c7Vendor (CNA)
Linux Linux8ba7b7c1dad1f6503c541778f31b33f7f62eb966Vendor (CNA)
Linux Linuxc5402fb5f71f1a725f1e55d9c6799c0c7bec308fVendor (CNA)
Linux Linuxfae05b2314b147a78fbed1dc4c645d9a66313758Vendor (CNA)
Linux Linuxfc658c083904427abbf8f18280d517ee2668677cVendor (CNA)
debian:linux5.18.2-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records