[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHyG7AzcQGmTHXaNccmPw9LP10gm3PFQS1t20sOCkups":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"eaeb34f4-6821-4506-970f-f33530463f9a","noisytcp-unpatched-linux-kernel-race-condition-enables-remote-server-crashes","05cfe55d-e2d1-434b-95ef-396c77870f5d","NoisyTCP: Unpatched Linux Kernel Race Condition Enables Remote Server Crashes","A race condition in the Linux kernel's TCP stack (CVE-2026-99288, 'NoisyTCP') allows any remote attacker to crash a server by sending specially crafted packets to any open port—no authentication required. The flaw has existed since Linux kernel 4.4, meaning systems that have not been kept current are exposed to a vulnerability with years of undetected presence. Because it targets the TCP layer itself, virtually every internet-facing Linux server or cloud VM running an unpatched kernel is at risk of denial-of-service. Patches are available in upstream kernel releases 6.12.117, 6.18.63, and 7.3.4, making prompt patching the most critical remediation step. The incident underscores how foundational OS-layer vulnerabilities can have sweeping impact across entire infrastructure estates if patch cycles are slow or inconsistent.","**Immediate actions:**\n- Apply the upstream Linux kernel patches (versions 6.12.117, 6.18.63, or 7.3.4) or your distribution's backported fix as an emergency change.\n- Audit all internet-facing Linux servers and cloud VMs to identify unpatched kernel versions using an authenticated vulnerability scanner.\n- Apply network-level mitigations (e.g., TCP rate limiting, firewall rules restricting unexpected source IPs) as a temporary compensating control until patching is complete.\n\n**Long-term improvements:**\n- Establish an emergency\u002Fout-of-band patching procedure with defined SLAs for critical kernel-level CVEs, separate from routine patch cycles.\n- Maintain a continuously updated inventory of all Linux systems, including kernel versions, so scope of exposure can be determined within hours of a disclosure.\n- Subscribe to kernel security mailing lists and vendor advisories to receive patch notifications the moment they are released.\n\n**Detection measures:**\n- Deploy host-based monitoring to alert on unexpected kernel panics, server reboots, or TCP stack anomalies that may indicate active exploitation.\n- Implement network traffic analysis to detect abnormal TCP packet patterns consistent with denial-of-service attempts targeting listening ports.",[12,13,14,15,16],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIS2 Article 21(2)(e)","NIST CSF 2.0 RS.MI-2: Incident Mitigation",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"NIST CSF 2.0 RS.MI-2: Incident Mitigation":20,"CIS Control 7: Continuous Vulnerability Management (v8)":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"NIS2 Article 21(2)(e) explicitly covers vulnerability handling and disclosure in acquisition, development, and maintenance; operators of critical services are required to have processes to act on kernel-level vulnerability disclosures like NoisyTCP promptly.","SI-2 requires organizations to identify, report, and correct information system flaws; applying available kernel patches within defined timeframes is exactly what this control mandates for a critical CVE like NoisyTCP.","NIST CSF 2.0 RS.MI-2 calls for mitigating the effects of incidents; having compensating network controls (rate limiting, firewall rules) ready to deploy while patches are applied directly limits the impact of active NoisyTCP exploitation attempts.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; a formal process here would have identified the NoisyTCP flaw in affected kernel versions and driven timely patching before exploitation.","CIS Control 2 requires maintaining an accurate inventory of software versions; knowing which systems run kernel versions older than 6.12.117\u002F6.18.63\u002F7.3.4 is a prerequisite to scoping and prioritizing the NoisyTCP patch effort.","published","2026-11-15T18:20:22.854147+00:00","2026-11-15T18:20:22.819+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.cyberkendra.com\u002F2026\u002F11\u002Fcve-2026-99288-noisytcp-linux-kernel-tcp-flaw.html","cve-2026-99288-noisytcp-linux-tcp-flaw-crashes-servers-e0d79f","CVE-2026-99288 NoisyTCP: Linux TCP Flaw Crashes Servers",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"5284decd-c470-4555-b6a3-f795dab9d138","2026-11-16","morning","ThreatNoir Morning Brief — November 16","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-16\u002Fthreatnoir-morning-brief-2026-11-16.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them."]