LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50001: netfilter: nft_tproxy: restrict to prerouting hook

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_tproxy: restrict to prerouting hook TPROXY is only allowed from prerouting, but nft_tproxy doesn't check this. This fixes a crash (null dereference) when using tproxy from e.g. output.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system when nftables TPROXY is used from an unsupported hook. The source describes a null pointer dereference, not data theft or remote code execution. Business impact is most likely availability risk on Linux hosts using nftables transparent proxy rules.

Executive priority

Treat as a targeted availability concern, not an emergency without local evidence. Prioritize internet-facing proxy, gateway, firewall, and load-balancing Linux hosts that use nftables TPROXY, then fold remaining systems into normal kernel patch cycles.

Technical view

nft_tproxy failed to enforce that TPROXY is restricted to the prerouting hook. Using it from another hook, such as output, could trigger a kernel null dereference. The provided record lists Linux kernel branches and stable commits but no CVSS, CWE, exploit status, or distribution package mapping.

Likely exposure

Exposure appears limited to Linux systems with affected kernel code where nftables TPROXY rules can be configured incorrectly or by an authorized actor. Distribution-specific exposure needs vendor package advisories because the bundle only lists upstream kernel versions and commits.

Exploitation context

The bundle does not show active exploitation, KEV listing, proof-of-concept status, or remote attack details. It supports a crash scenario caused by using TPROXY from an unsupported hook, which points to availability impact rather than confirmed compromise.

Researcher notes

Key evidence is narrow: nft_tproxy lacked hook validation and could crash on unsupported hook use. The record lacks CVSS and exploitability detail, so validation should focus on kernel lineage, nftables rule paths, and whether local configuration privileges are required.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-50001 package status.
  • Update affected kernels to vendor-supported fixed builds when available.
  • Review nftables TPROXY rules for use outside prerouting.
  • Restrict who can modify firewall and nftables configuration.
  • Monitor kernel logs for null dereference crashes tied to nft_tproxy.

Validation and detection

  • Inventory Linux kernel versions on systems using nftables or TPROXY.
  • Confirm whether vendor kernels include the referenced upstream stable fixes.
  • Audit nftables rules for TPROXY usage in non-prerouting hooks.
  • Check crash logs for nft_tproxy or netfilter null dereference indicators.
  • Document systems where transparent proxying is business-critical.
Prepared
Confidence
medium
Sources
8

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-50001 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
7Source 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
LinuxLinux4ed8eb6570a49931c705512060acd50058d61616, 4ed8eb6570a49931c705512060acd50058d61616, 4ed8eb6570a49931c705512060acd50058d61616, 4ed8eb6570a49931c705512060acd50058d61616, 4ed8eb6570a49931c705512060acd50058d61616, 4ed8eb6570a49931c705512060acd50058d61616unaffected
LinuxLinux4.19, 0, 4.19.273, 5.4.232, 5.10.169, 5.15.95, 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.