CVE-2024-36270: netfilter: tproxy: bail out if IP has been disabled on the device
In the Linux kernel, the following vulnerability has been resolved:
netfilter: tproxy: bail out if IP has been disabled on the device
syzbot reports:
general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
[..]
RIP: 0010:nf_tproxy_laddr4+0xb7/0x340 net/ipv4/netfilter/nf_tproxy_ipv4.c:62
Call Trace:
nft_tproxy_eval_v4 net/netfilter/nft_tproxy.c:56 [inline]
nft_tproxy_eval+0xa9a/0x1a00 net/netfilter/nft_tproxy.c:168
__in_dev_get_rcu() can return NULL, so check for this.
Security readout for executives and security teams
Plain-English summary
CVE-2024-36270 is a Linux kernel netfilter TPROXY flaw where a missing null check can crash kernel code when IP is disabled on a device. Business impact is most relevant for Linux systems that use firewalling, routing, proxying, or appliance networking features.
Executive priority
Prioritize assessment for Linux network infrastructure and appliances because kernel faults can affect availability. Urgency is below known-exploited issues unless vendor guidance identifies exposed products or critical operational dependency.
Technical view
The issue is in nf_tproxy_laddr4 within IPv4 netfilter TPROXY handling. The CVE states __in_dev_get_rcu() can return NULL, causing a KASAN-reported null pointer dereference and general protection fault. Kernel stable commits add the required bail-out behavior.
Likely exposure
Exposure is likely limited to Linux systems using netfilter/nftables TPROXY paths, especially networking appliances, gateways, or embedded products. The source bundle lists Linux as affected and includes Siemens advisories, but it does not provide a complete product exposure matrix.
Exploitation context
The provided sources do not show CISA KEV listing, public exploitation, exploit maturity, or attack prerequisites. Treat this as a kernel stability and availability risk until vendor advisories clarify practical exploitability in your environment.
Researcher notes
Primary evidence is a kernel syzbot crash trace and the upstream fix rationale: __in_dev_get_rcu() may return NULL. The bundle lacks CVSS, CWE, exploitability details, and distribution-specific fixed package versions, so avoid over-scoping beyond TPROXY-related Linux exposure.
Mitigation direction
Update affected Linux kernels using vendor-supported packages containing the referenced stable fixes.
Check Linux distribution advisories for backported fixes before relying on upstream version numbers.
Review Siemens SSA-265688 and SSA-613116 if using Siemens affected products.
Prioritize systems performing routing, firewalling, transparent proxying, or appliance networking roles.
Track vendor guidance where no product-specific fix is named in the source bundle.
Validation and detection
Inventory Linux kernel versions across servers, appliances, containers hosts, and embedded systems.
Confirm whether netfilter or nftables TPROXY functionality is configured or required.
Verify installed kernels include the relevant upstream stable commit or vendor backport.
Check whether interfaces can operate with IP disabled in affected traffic paths.
Document Siemens product applicability against the two referenced Siemens advisories.
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-2024-36270 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.