CVE-2024-50251: netfilter: nft_payload: sanitize offset and length before calling skb_checksum()
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_payload: sanitize offset and length before calling skb_checksum()
If access to offset + length is larger than the skbuff length, then
skb_checksum() triggers BUG_ON().
skb_checksum() internally subtracts the length parameter while iterating
over skbuff, BUG_ON(len) at the end of it checks that the expected
length to be included in the checksum calculation is fully consumed.
Security readout for executives and security teams
Plain-English summary
CVE-2024-50251 is a Linux kernel netfilter flaw where malformed payload checksum parameters can hit a kernel BUG condition. The practical business concern is service disruption, not confirmed data theft. The source bundle does not provide CVSS, CWE, or active exploitation evidence.
Executive priority
Treat as a timely kernel stability patching item. Prioritize internet-facing, multi-tenant, and operational technology systems, but do not classify as emergency exploitation based on the supplied evidence alone.
Technical view
In nft_payload, offset and length were not sanitized before skb_checksum(). When offset plus length exceeds the skbuff length, skb_checksum() can finish with unconsumed length and trigger BUG_ON(len). Kernel stable commits add bounds handling across maintained branches.
Likely exposure
Exposure is most likely on Linux systems running affected kernel branches before the referenced stable fixes, especially systems using netfilter/nftables. Debian LTS and Siemens advisories indicate downstream impact. The provided evidence does not prove all Linux deployments are exploitable.
Exploitation context
CISA KEV status is false in the bundle. A public GitHub PoC reference exists, so researcher interest is visible, but the supplied sources do not confirm active exploitation, remote reachability, or required privileges.
Researcher notes
The root issue is missing offset and length validation before skb_checksum() in nft_payload. Assess branch-specific fixes from kernel stable commits. Avoid assuming exploitability conditions; the bundle lacks privilege, namespace, and remote-trigger details.
Mitigation direction
Update Linux kernels to vendor releases containing the referenced stable fixes.
Apply relevant Debian LTS or device-vendor advisories for managed distributions and appliances.
Check Siemens advisories for affected industrial products before scheduling firmware changes.
If no vendor fix is available, follow vendor mitigation guidance and reduce nftables exposure where practical.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Compare deployed kernels against vendor advisories and referenced fixed stable branches.
Identify systems using nftables or netfilter rules that process packet payload checksums.
Confirm patched kernels are booted, not only installed.
Track vendor advisories for products that embed Linux kernels.
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-50251 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
2ADP providers
15Source 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.
Nov 9, 2024, 10:14 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.