LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50007: xfrm: fix refcount leak in __xfrm_policy_check()

In the Linux kernel, the following vulnerability has been resolved: xfrm: fix refcount leak in __xfrm_policy_check() The issue happens on an error path in __xfrm_policy_check(). When the fetching process of the object `pols[1]` fails, the function simply returns 0, forgetting to decrement the reference count of `pols[0]`, which is incremented earlier by either xfrm_sk_policy_lookup() or xfrm_policy_lookup(). This may result in memory leaks. Fix it by decreasing the reference count of `pols[0]` in that path.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the IPsec/XFRM policy path. On a specific error path, the kernel can forget to release a reference, causing a memory leak. The public record does not provide CVSS, CWE, exploitability details, or evidence of active exploitation.

Executive priority

Treat this as a routine kernel hygiene item unless your environment heavily depends on IPsec/XFRM or shows unexplained kernel memory pressure. Patch through normal vendor kernel channels after confirming applicability.

Technical view

The flaw is a reference-count leak in __xfrm_policy_check(). If fetching pols[1] fails, the function returns without decrementing pols[0], previously acquired by xfrm_sk_policy_lookup() or xfrm_policy_lookup(). The fix releases pols[0] on that failure path.

Likely exposure

Exposure is limited to Linux kernel systems containing the affected XFRM policy code. The source lists Linux kernel versions and stable fix commits, but distro backports and packaged kernel status require vendor confirmation.

Exploitation context

The source only states that the bug may result in memory leaks. It does not describe active exploitation, public exploit code, attacker requirements, privilege requirements, or practical denial-of-service impact. KEV status is false.

Researcher notes

Evidence is narrow: the public record documents a memory leak fix but no CVSS vector, CWE, exploit scenario, or runtime trigger conditions. Avoid overstating impact beyond potential memory leakage in the XFRM policy-check error path.

Mitigation direction

  • Update to a Linux kernel release containing the referenced stable fixes.
  • Check distribution advisories for backported kernel packages covering CVE-2022-50007.
  • Prioritize internet-facing or IPsec/XFRM-using systems once vendor applicability is confirmed.
  • Monitor kernel memory pressure until patched if affected systems cannot be updated quickly.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, containers hosts, and network nodes.
  • Compare installed kernels against vendor advisories for CVE-2022-50007.
  • Confirm whether vendor kernels include the referenced XFRM refcount fix.
  • Review kernel update history for the stable commit or equivalent backport.
Prepared
Confidence
medium
Sources
10

Public sources used

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-50007 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
9Source 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
LinuxLinux134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3d, 134b0fc544ba062498451611cb6f3e4454221b3dunaffected
LinuxLinux2.6.19, 0, 4.9.327, 4.14.292, 4.19.257, 5.4.212, 5.10.140, 5.15.64, 5.19.6, 6.0affected
Weakness

CWE details

No CWE listed

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