Security readout for executives and security teams
Plain-English summary
CVE-2022-49871 is a Linux kernel memory leak in the TUN network driver path. A local user or process with relevant access could trigger leaked kernel memory and degrade availability over time. The source rates it medium, with high availability impact but no confidentiality or integrity impact.
Executive priority
Patch through the normal kernel maintenance process, with accelerated handling for multi-tenant or user-accessible systems. There is no source evidence of active exploitation, but the availability impact justifies timely remediation.
Technical view
The bug is in net/tun handling of napi_get_frags. After napi_gro_frags can leave entries on napi->rx_list, tun_napi_del deletes NAPI without completing pending GRO work, leaking skb allocations. The kernel fix adds napi_complete after napi_gro_frags.
Likely exposure
Exposure is mainly Linux systems running affected kernel builds where local low-privileged users or processes can exercise the TUN driver path. The bundle lists Linux kernel versions including 4.15, 4.19.267, 5.4.225, 5.10.155, 5.15.79, 6.0.9, and 6.1-era entries.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact. The bundle does not indicate CISA KEV listing or active exploitation. Treat this as a local denial-of-service risk, not remote code execution.
Researcher notes
Evidence is limited to the CVE record and Linux stable references. The root cause is cleanup ordering around NAPI GRO fragments in tun_get_user and tun_napi_del. Validate against downstream vendor kernels because distribution backports may not match upstream version strings.
Mitigation direction
Apply a vendor kernel update that includes the referenced upstream stable fixes.
Check your Linux distribution advisory for exact fixed package versions.
Prioritize hosts with untrusted local users, containers, VPNs, or TUN usage.
Limit unnecessary access to TUN devices while awaiting vendor guidance.
Validation and detection
Inventory Linux kernel versions across exposed fleets.
Map kernels to vendor advisories and the referenced stable commits.
Confirm whether TUN/TAP functionality is enabled or reachable by local users.
Review monitoring for unexplained kernel memory growth or availability degradation.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.