A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected.
Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
3.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc33.10.223.11.173.12.153.13.163.14.83.15.0-rc3Exploitability
AV:NAC:HAT:PPR:NUI:NVulnerable System
VC:HVI:HVA:LSubsequent System
SC:NSI:NSA:N9.2/CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NMemory Safety