Security readout for executives and security teams
Plain-English summary
Linux’s FOU UDP tunnelling code accepted an invalid protocol value of zero. In that state, a received packet buffer was neither released nor passed onward. This may consume resources and affect availability, but the supplied sources do not quantify impact or establish remote exploitability.
Executive priority
Begin targeted inventory and patch planning promptly, especially for systems using FOU. Treat this as kernel availability risk requiring remediation, but not as a confirmed emergency: severity, attacker reachability, and exploitation are unverified. Escalate priority if vendor guidance identifies exposed products or operational monitoring shows abnormal networking-memory consumption.
Technical view
When FOU_ATTR_IPPROTO equals zero, fou_udp_recv() neither frees the skb nor resubmits it through ip_protocol_deliver_rcu(). The upstream correction rejects zero during FOU configuration. The supplied record identifies affected Linux releases and several stable-branch fixes, but does not provide CVSS scoring or complete distribution-specific version mapping.
Likely exposure
Potential exposure is limited to Linux systems using the FOU networking feature where the invalid FOU_ATTR_IPPROTO value can be configured. The sources do not establish whether configuration requires privileges, whether ordinary network traffic can trigger the condition, or which distribution package versions remain vulnerable.
Exploitation context
The supplied record does not identify active exploitation, and the CVE is not marked as included in KEV. No exploit proof, attack prerequisites, or demonstrated business impact is provided. Resource exhaustion is a plausible inference from retained packet buffers, not a quantified outcome in the supplied evidence.
Researcher notes
This is an input-validation and packet-lifecycle defect. The fix forbids protocol zero rather than adding cleanup inside fou_udp_recv(). Important unanswered questions include who can set the attribute, how traffic reaches the affected path, whether skb retention is persistent, the depletion rate, and practical denial-of-service reproducibility. Distribution backport status must be assessed separately.
Mitigation direction
- Install a vendor-supported kernel build incorporating the applicable referenced stable fix.
- Use distribution or appliance advisories to map the running package to a corrected build.
- Follow vendor guidance for any required reboot, service restart, or temporary mitigation.
- Prioritize systems confirmed to configure or depend on FOU networking.
Validation and detection
- Inventory kernel package versions and identify systems where FOU networking is configured.
- Compare each vendor build against its advisory and the applicable stable fix commit.
- Confirm corrected code rejects FOU_ATTR_IPPROTO value zero.
- After updating, verify FOU-dependent networking services operate normally.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-23083 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
SSVC decision data
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c7498f9bc390479ccfad7c7f2332237ff4945b03CVE reference, Linux
- https://git.kernel.org/stable/c/611ef4bd9c73d9e6d87bed57a635ff1fdd8c91eaCVE reference, Linux
- https://git.kernel.org/stable/c/6e983789b7588ee59cbf303583546c043bad8e19CVE reference, Linux
- https://git.kernel.org/stable/c/1cc98b8887cabb1808d2f4a37cd10a7be7574771CVE reference, Linux
- https://git.kernel.org/stable/c/b7db31a52c3862a1a32202a273a4c32e7f5f4823CVE reference, Linux
- https://git.kernel.org/stable/c/9b75dff8446ec871030d8daf5a69e74f5fe8b956CVE reference, Linux
- https://git.kernel.org/stable/c/7a9bc9e3f42391e4c187e099263cf7a1c4b69ff5CVE reference, Linux
- https://cert-portal.siemens.com/productcert/html/ssa-019113.htmlCVE reference, siemens-SADP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.