PatchSiren cyber security CVE debrief
CVE-2026-99031 Linux CVE debrief
A vulnerability in the Linux kernel's net: bridge implementation could lead to a stack guard page hit when a large number of STAR_EXCL ports are present. This occurs due to recursive multicast port cleanup. The issue is resolved by keeping the complete port-group deletion path for cleanup but suppressing S,G exclude-port cleanup while the helper is walking the same entry.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-23
- Original CVE updated
- 2026-10-30
- Advisory published
- 2026-10-23
- Advisory updated
- 2026-10-30
Who should care
Defenders responsible for Linux kernel infrastructure, particularly those managing bridge configurations with high numbers of STAR_EXCL ports, should assess exposure and prioritize patching affected versions.
Why it matters
This vulnerability in the Linux kernel's net: bridge implementation could lead to system instability due to recursive multicast port cleanup. Defenders managing Linux kernel infrastructure, especially those with high numbers of STAR_EXCL ports in bridge configurations, should assess exposure and prioritize patching affected versions.
- Potential for stack guard page hits leading to system instability.
- Need for verification of Linux kernel versions and bridge configurations.
- Priority for patching affected versions to prevent potential issues.
Technical summary
The Linux kernel's net: bridge implementation has a vulnerability that could lead to a stack guard page hit due to recursive multicast port cleanup when a large number of STAR_EXCL ports are present. The issue is addressed by maintaining the complete port-group deletion path for cleanup while suppressing S,G exclude-port cleanup during the same helper walk. This vulnerability in the Linux kernel's net: bridge implementation could lead to system instability due to recursive multicast port cleanup. Defenders managing Linux kernel infrastructure, especially those with high numbers of STAR_EXCL ports in bridge configurations, should assess exposure and prioritize patching affected versions.
Defensive priority
Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly those with high numbers of STAR_EXCL ports in their bridge configurations.
Recommended defensive actions
- Verify and apply patches for affected Linux kernel versions.
- Review bridge configurations for high numbers of STAR_EXCL ports.
- Monitor for potential stack guard page hits in Linux kernel logs.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The CVE record and source item provide details on the vulnerability and its resolution in the Linux kernel. Multiple source references from the Linux kernel's Git repository are available, detailing the specific commits that address the issue.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-99031 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-99031
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-99031 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-99031
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
net: bridge: avoid recursive multicast port cleanup
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/99xxx/CVE-2026-99031.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0ed8edcbcf2290dba13c1beeba27fc19ad38515b
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6a7385f6605958aa69eeb185c91f45d77640d1e2
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/26142868b0767e95e28b7a1237f58b292b54d1d9
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/695a5a4c69c922d9296b2d7ad5f1ce8c6858fc64
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2fb87c6025f90191516bee3ce14b42eb3e1cfed7
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d109141ba14652146089ef78b32d5e4d5285ebad
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7931fb9181421953f3133b408b0f2e2b8dd68b61
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.