BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49917High confidence

ipvs: fix WARNING in ip_vs_app_net_cleanup()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-49917 · CSAF 2.0 · revision 45 · interimSUSE Product Security TeamCVE-2022-49917
291 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: ipvs: fix WARNING in ip_vs_app_net_cleanup() During the initialization of ip_vs_app_net_init(), if file ip_vs_app fails to be created, the initialization is successful by default. Therefore, the ip_vs_app file doesn't be found during the remove in ip_vs_app_net_cleanup(). It will cause WRNING. The following is the stack information: name 'ip_vs_app' WARNING: CPU: 1 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: 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
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-12876

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix WARNING in ip_vs_app_net_cleanup() During the initialization of ip_vs_app_net_init(), if file ip_vs_app fails to be created, the initialization is successful by default. Therefore, the ip_vs_app file doesn't be found during the remove in ip_vs_app_net_cleanup(). It will cause WRNING. The following is the stack information: name 'ip_vs_app' WARNING: CPU: 1 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> 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>

What

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix WARNING in ip_vs_app_net_cleanup() During the initialization of ip_vs_app_net_init(), if file ip_vs_app fails to be created, the initialization is successful by default. Therefore, the ip_vs_app file doesn't be found during the remove in ip_vs_app_net_cleanup(). It will cause WRNING. The following is the stack information: name 'ip_vs_app' WARNING: CPU: 1 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> 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>

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: ipvs: fix WARNING in ip_vs_app_net_cleanup() During the initialization of ip_vs_app_net_init(), if file ip_vs_app fails to be created, the initialization is successful by default. Therefore, the ip_vs_app file doesn't be found during the remove in ip_vs_app_net_cleanup(). It will cause WRNING. The following is the stack information: name 'ip_vs_app' WARNING: CPU: 1 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> 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>

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0922Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250507Security Bulletin 07 May 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 May 2025, published on 7 May 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49901 Référence CVE CVE-2022-49902 https://www.cve.org/CVERecord?id=CVE-2022-49902 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0607Multiples vulnérabilités dans le noyau Linux de SUSE

rd?id=CVE-2022-4662 Référence CVE CVE-2022-49154 https://www.cve.org/CVERecord?id=CVE-2022-49154 Référence CVE CVE-2022-49622 https://www.cve.org/CVERecord?id=CVE-2022-49622 Référence CVE CVE-2022-49731 https://www.cve.org/CVERecord?id=CVE-2022-49731 Référence CVE CVE-2022-49764 https://www.cve.org/CVERecord?id=CVE-2022-49764 Référence CVE CVE-2022-49780 https://www.cve.org/CVERecord?id=CVE-2022-49780 Référence CVE CVE-2022-49814 https://www.cve.org/CVERecord?id=CVE-2022-49814 Référence CVE CVE-2022-49879 https://www.cve.org/CVERecord?id=CVE-2022-49879 Référence CVE CVE-2022-49881 https://www.cve.org/CVERecord?id=CVE-2022-49881 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49934 https://www.cve.org/CVERecord?id=CVE-2022-49934 Référence CVE CVE-2022-49935 https://www.cve.org/CVERecord?id=CVE-2022-49935 Référence CVE CVE-2022-49936 https://www.cve.org/CVERecord?id=CVE-2022-49936 Référence CVE CVE-2022-49937 https://www.cve.org/CVERecord?id=CVE-2022-49937 Référence CVE CVE-2022-49938 https://www.cve.org/CVERecord?id=CVE-2022-49938 Référence CVE CVE-2022-49940 https://www.cve.org/CVERecord?id=CVE-2022-49940 Référence CVE CVE-2022-49942 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0560Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49901 Référence CVE CVE-2022-49902 https://www.cve.org/CVERecord?id=CVE-2022-49902 Référence CVE CVE-2022-49905 https://www.cve.org/CVERecord?id=CVE-2022-49905 Référence CVE CVE-2022-49906 https://www.cve.org/CVERecord?id=CVE-2022-49906 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0529Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49906 Référence CVE CVE-2022-49907 https://www.cve.org/CVERecord?id=CVE-2022-49907 Référence CVE CVE-2022-49908 https://www.cve.org/CVERecord?id=CVE-2022-49908 Référence CVE CVE-2022-49909 https://www.cve.org/CVERecord?id=CVE-2022-49909 Référence CVE CVE-2022-49910 https://www.cve.org/CVERecord?id=CVE-2022-49910 Référence CVE CVE-2022-49913 https://www.cve.org/CVERecord?id=CVE-2022-49913 Référence CVE CVE-2022-49914 https://www.cve.org/CVERecord?id=CVE-2022-49914 Référence CVE CVE-2022-49915 https://www.cve.org/CVERecord?id=CVE-2022-49915 Référence CVE CVE-2022-49916 https://www.cve.org/CVERecord?id=CVE-2022-49916 Référence CVE CVE-2022-49917 https://www.cve.org/CVERecord?id=CVE-2022-49917 Référence CVE CVE-2022-49918 https://www.cve.org/CVERecord?id=CVE-2022-49918 Référence CVE CVE-2022-49921 https://www.cve.org/CVERecord?id=CVE-2022-49921 Référence CVE CVE-2022-49922 https://www.cve.org/CVERecord?id=CVE-2022-49922 Référence CVE CVE-2022-49923 https://www.cve.org/CVERecord?id=CVE-2022-49923 Référence CVE CVE-2022-49924 https://www.cve.org/CVERecord?id=CVE-2022-49924 Référence CVE CVE-2022-49925 https://www.cve.org/CVERecord?id=CVE-2022-49925 Référence CVE CVE-2022-49927 https://www.cve.org/CVERecord?id=CVE-2022-49927 Référence CVE CVE-2022-49928 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026731Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.24, 4.19.265 ≤ 4.19.*, 5.4.224 ≤ 5.4.*, 5.10.154 ≤ 5.10.*, 5.15.78 ≤ 5.15.*, 6.0.8 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2025 · Last source change 11 May 2026, 19:09 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-12876
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-12876↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49917 · cve.blacktree.nl