Vulnerability briefing · 2026-10-28 16:47 IST

CVE-2026-99165

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate output stream after association connect wait When message interleaving is enabled, the first send waits for association establishment before building its data chunks. The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count. sctp_stream_init() then frees the extension of every removed stream. The sender resumes with the stream that it checked before the wait. If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension. Fatal-oops policies then panic the host. KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace: sctp_primitive_SEND sctp_sendmsg_to_asoc sctp_sendmsg A range check alone is insufficient. Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink. The stream can then be in range while its extension remains NULL. The send-buffer wait has the same issue. Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock. Once the lock is reacquired, the validation remains stable through data creation and queueing. If validation fails after the connect wait, the auto-created association is already established. Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.

UNRATED · N/ALinux

Executive briefing

This record describes a reported software or hardware weakness. The description and CVSS rating are source metadata; practical risk depends on whether your environment uses an affected product/version and whether the vulnerable component is reachable and configured in an exploitable way.

Assessment status: No CISA KEV listing is currently recorded in this local feed. This does not prove the vulnerability is not exploited.

Severity & exploitability

— / 10 CVSS

CVSS vector:

Impacted products and platforms

Specific affected product configurations are not currently available in the NVD record. Review vendor advisories and validate applicability against your asset inventory.

How it works and what it could affect

The NVD description is the authoritative short summary currently available for this record. A detailed technical mechanism is not inferred when the source record does not provide one.

Review the CVSS attack characteristics above to understand whether exploitation is network/local, whether privileges or user interaction are required, and which confidentiality, integrity or availability impacts are scored.

Remediation and recommended response

  1. Identify exposure: compare the affected product and version ranges below with your asset inventory, software bill of materials, endpoint inventory and externally exposed services.
  2. Remediate: review the linked vendor security advisory or patch notes, upgrade to a fixed release, or apply the vendor-provided workaround if an upgrade cannot be completed.
  3. Mitigate while patching: restrict network access to the vulnerable service, disable the affected feature where operationally safe, and monitor vendor/CERT advisories for updated guidance.
  4. Validate: confirm the fixed version or mitigation on representative systems, run a vulnerability rescan, and retain change evidence.

No vendor remediation link has been identified in the available NVD references yet. Check the affected vendor's security advisory portal before applying changes.

Exploit intelligence & references

No CISA KEV match is recorded in the latest successful catalog refresh. This is not a guarantee that public proof-of-concept code or exploitation does not exist.

Sources: NVD and CISA KEV when available. Vendor confirmation remains the final authority for fixed versions and workarounds.

Open NVD record ← Back to CVE Watch

Threat intelligence, made actionable · CVE data sourced from the NVD