LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49918: ipvs: fix WARNING in __ip_vs_cleanup_batch()

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>

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

Analyst readout for executives and security teams

Plain-English summary

This Linux kernel issue affects IPVS cleanup after partial initialization failure. The documented result is a kernel warning when cleanup tries to remove a proc entry that was never created. The public sources do not provide CVSS, CWE, confirmed exploitation, or a clear business-impact scenario, so urgency should be driven by kernel exposure and vendor patch availability.

Executive priority

Track and remediate through normal kernel patch management unless vendor guidance raises severity. There is no source-backed evidence here of active exploitation or critical impact.

Technical view

In IPVS, ip_vs_conn_net_init() could treat failed creation of ip_vs_conn or ip_vs_conn_sync as successful. Later, __ip_vs_cleanup_batch() attempted removal and triggered remove_proc_entry() warnings for missing entries. The fix is represented by Linux stable commits listed in the CVE record. No exploit primitive or escalation path is described in the provided sources.

Likely exposure

Exposure is most plausible on Linux systems running affected kernel branches with IPVS present or enabled, especially load-balancing or container/network-namespace environments. The bundle lists Linux as affected but does not map distro package versions or configurations.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. It describes a warning during cleanup, not a published exploitation technique. Treat exploitation status as unconfirmed.

Researcher notes

Evidence is narrow: a Linux stable fix and stack trace for a cleanup warning. The bundle lacks CVSS, CWE, exploitability analysis, distro status, and proof of security impact beyond the resolved kernel warning.

Mitigation direction

  • Check Linux vendor advisories for CVE-2022-49918 coverage.
  • Upgrade to a kernel package containing the relevant stable fix.
  • Prioritize hosts using IPVS, load balancing, or network namespaces.
  • Avoid assuming non-listed distro kernels are safe without vendor mapping.

Validation and detection

  • Inventory deployed Linux kernel versions and vendor package revisions.
  • Determine whether IPVS modules or configurations are present.
  • Map installed kernels to the listed stable commits or vendor fixes.
  • Review kernel logs for __ip_vs_cleanup_batch or remove_proc_entry warnings.
Prepared
Confidence
medium
Sources
8

Public sources used

Based on public source material and reviewed before publication.

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-49918 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
0ADP providers
7Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux61b1ab4583e275af216c8454b9256de680499b19, 61b1ab4583e275af216c8454b9256de680499b19, 61b1ab4583e275af216c8454b9256de680499b19, 61b1ab4583e275af216c8454b9256de680499b19, 61b1ab4583e275af216c8454b9256de680499b19, 61b1ab4583e275af216c8454b9256de680499b19unaffected
LinuxLinux2.6.39, 0, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8, 6.1affected
Weakness

CWE details

No CWE listed

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