dbcve.org
Linux KernelOperating system · Linux

CVE-2022-49918

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-01
Fix available
A fix is available. Upgrade to 4.19.265 / 5.4.224 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: ipvs: fix WARNING in __ip_vs_cleanup_batch() During the initialization of ip_vs_conn_net_init(), if file ip_vs_conn or ip_vs_conn_sync fails to be created, the initialization is successful by default. Therefore, the ip_vs_conn or ip_vs_conn_sync file doesn't be found during the remove. The following is the stack information: name 'ip_vs_conn_sync' WARNING: CPU: 3 PID: 9 at fs/proc/generic.c:712 remove_proc_entry+0x389/0x460 Modules linked in: Workqueue: netns cleanup_net RIP: 0010:remove_proc_entry+0x389/0x460 Call Trace: <TASK> __ip_vs_cleanup_batch+0x7d/0x120 ops_exit_list+0x125/0x170 cleanup_net+0x4ea/0xb00 process_one_work+0x9bf/0x1710 worker_thread+0x665/0x1080 kthread+0x2e4/0x3a0 ret_from_fork+0x1f/0x30 </TASK>

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

A detailed technical summary for this CVE is being prepared.

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:>= 2.6.39, < 4.19.265>= 4.20, < 5.4.224>= 5.5, < 5.10.154>= 5.11, < 5.15.78>= 5.16, < 6.0.8= 6.1

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.265 / 5.4.224 / 5.10.154 or later
Fixed in 4.19.2655.4.2245.10.154
Vendor patch git.kernel.org →
Recommended fix High confidence

4.19.265+ / 5.4.224+ / 5.10.154+ / 5.15.78+ (or any newer stable release)

  1. Identify the currently running kernel version using 'uname -r'
  2. Determine which branch your current kernel belongs to (e.g., 4.19.x, 5.4.x, 5.10.x, 5.15.x)
  3. Upgrade to a fixed kernel version: For 4.19.x branch -> 4.19.265 or later; For 5.4.x branch -> 5.4.224 or later; For 5.10.x branch -> 5.10.154 or later; For 5.15.x branch -> 5.15.78 or later; For newer branches (5.16+) the fix is already included
  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 'zypper update kernel-default' for SUSE)
  5. Reboot the system to load the new kernel
  6. Verify the new kernel version is running with 'uname -r'
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with custom modules or older drivers; test in staging first

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 $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-49918 — 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-49918 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