CVE-2022-49903: ipv6: fix WARNING in ip6_route_net_exit_late()
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix WARNING in ip6_route_net_exit_late()
During the initialization of ip6_route_net_init_late(), if file
ipv6_route or rt6_stats fails to be created, the initialization is
successful by default. Therefore, the ipv6_route or rt6_stats file
doesn't be found during the remove in ip6_route_net_exit_late(). It
will cause WRNING.
The following is the stack information:
name 'rt6_stats'
WARNING: CPU: 0 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
PKRU: 55555554
Call Trace:
<TASK>
ops_exit_list+0xb0/0x170
cleanup_net+0x4ea/0xb00
process_one_work+0x9bf/0x1710
worker_thread+0x665/0x1080
kthread+0x2e4/0x3a0
ret_from_fork+0x1f/0x30
</TASK>
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can trigger a kernel warning during IPv6 network namespace cleanup when expected proc files were not created during initialization. The public record does not show code execution, privilege escalation, data exposure, CVSS scoring, or known exploitation.
Executive priority
Treat as a maintenance-priority kernel update until stronger impact evidence appears. There is no supplied evidence of exploitation or severe business impact, but kernel hygiene remains important on shared infrastructure.
Technical view
The bug is in IPv6 route proc cleanup. If ipv6_route or rt6_stats creation fails during ip6_route_net_init_late(), later ip6_route_net_exit_late() may try to remove a missing proc entry and trigger remove_proc_entry WARNING during netns cleanup.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or branches listed in the CVE record. The bundle provides upstream stable commit references but no package names, CPEs, or distribution-specific advisories.
Exploitation context
No active exploitation is supported by the supplied sources. KEV is false, and the source bundle describes a kernel warning condition rather than a demonstrated attack path.
Researcher notes
The record lacks CVSS, CWE, CPEs, exploit evidence, and distribution package mappings. The described failure path is initialization error handling followed by cleanup of absent proc entries, producing a warning in remove_proc_entry.
Mitigation direction
Update to a Linux kernel containing the referenced upstream stable fixes.
Check Linux distribution advisories for backported package versions.
Prioritize systems using IPv6 and network namespace-heavy workloads.
Include this in routine kernel patch cycles unless vendor guidance raises severity.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Compare running kernels with vendor advisories and referenced stable commits.
Review kernel logs for related IPv6 route cleanup warnings.
Confirm distribution packages include the upstream fix or a documented backport.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-49903 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2025, 14:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.