CVE-2026-23125 Linux CVE debrief

Who should care

Linux kernel developers, maintainers, and distribution maintainers should assess exposure and prioritize verification of affected versions and apply patches or mitigations. Linux distribution maintainers should verify and apply patches or mitigations. Security teams and vulnerability management teams should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

The Linux kernel's SCTP transmit path is vulnerable to a null-pointer dereference when SCTP-AUTH key initialization fails. Linux kernel developers, maintainers, and distribution maintainers should assess exposure and prioritize verification of affected versions and apply patches or mitigations.

• Verify Linux kernel versions to determine exposure
• Assess SCTP-AUTH key initialization failures for potential null-pointer dereferences
• Apply patches or mitigations to prevent exploitation
• Monitor SCTP transmit path for potential issues

Technical summary

The Linux kernel's SCTP transmit path is vulnerable to a null-pointer dereference when SCTP-AUTH key initialization fails. This occurs due to the SCTP_CMD_ASSOC_SHKEY command being moved right after SCTP_CMD_PEER_INIT. The vulnerability affects Linux kernel versions and requires verification from official sources. Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions, while Linux distribution maintainers should verify and apply patches or mitigations. The issue is triggered when sctp_auth_asoc_init_active_key() fails in sctp_s.

Defensive priority

Linux kernel developers and maintainers should assess exposure and prioritize verification of affected versions, while Linux distribution maintainers should verify and apply patches or mitigations.

Recommended defensive actions

• Verify Linux kernel versions and assess exposure
• Apply patches or mitigations provided by Linux distribution maintainers
• Monitor SCTP-AUTH key initialization for potential failures
• 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 vulnerability was reported in the Linux kernel's SCTP transmit path. The issue occurs when SCTP-AUTH key initialization fails, leading to a null-pointer dereference. The affected versions require verification from official sources.

Sources and references

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.