CVE-2022-49199: RDMA/nldev: Prevent underflow in nldev_stat_set_counter_dynamic_doit()
In the Linux kernel, the following vulnerability has been resolved:
RDMA/nldev: Prevent underflow in nldev_stat_set_counter_dynamic_doit()
This code checks "index" for an upper bound but it does not check for
negatives. Change the type to unsigned to prevent underflows.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49199 is a Linux kernel RDMA/nldev bug caused by an index value being checked only for being too large, not for being negative. The public record does not provide CVSS, confirmed impact, or attack prerequisites, so business risk cannot be rated confidently from these sources alone.
Executive priority
Treat this as a kernel hygiene item unless your environment uses RDMA heavily or runs affected upstream kernels. The lack of CVSS, KEV status, and stated impact makes emergency action unsupported by the supplied evidence.
Technical view
The issue is in nldev_stat_set_counter_dynamic_doit(). A signed index passed validation against an upper bound but could underflow if negative. The kernel fix changes the type to unsigned to prevent that condition. The source bundle lists Linux kernel versions around 5.16, 5.17.2, and 5.18 as affected, with stable commit references.
Likely exposure
Likely exposure is limited to Linux systems running affected kernel builds that include the vulnerable RDMA/nldev code path. The supplied sources do not state whether RDMA hardware, specific privileges, namespaces, or local access are required.
Exploitation context
The bundle marks KEV as false and includes no cited evidence of active exploitation, public exploit availability, or real-world abuse. It also does not describe the security impact beyond preventing an underflow.
Researcher notes
The key uncertainty is exploitability. The public description identifies a signedness/underflow bug and its code-level fix, but does not document reachable inputs, privilege boundary, crashability, memory corruption, or confidentiality/integrity impact.
Mitigation direction
Check distribution advisories for CVE-2022-49199 and backported kernel fixes.
Upgrade to a vendor-supported kernel containing the referenced stable fixes.
Prioritize systems using RDMA or exposing RDMA management functionality.
Document any temporary risk acceptance where kernel updates are delayed.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Compare installed kernels against vendor advisories and referenced stable commits.
Identify hosts with RDMA drivers, hardware, or related services enabled.
Confirm patched kernels after reboot using approved asset tooling.
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-49199 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
4Source 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.
Feb 26, 2025, 01:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.