1.3.4

Security fix

A local user able to open the driver's device could deadlock the system, hanging the host
until it was power-cycled. The driver held its device lock across a socket send, so a packet
the transport delivered back to the driver on the same thread asked for a lock that thread
already held. Fixed by holding a reference on the socket for the send instead of the lock.

This affects every 1.x release. Users who cannot update should move to 2.8.13 or later,
which carries the same fix.

• driver: do not hold the device lock across a socket send (CVE-2026-105390)

Full Changelog: 1.3.3...1.3.4