PT-2026-43758 · Linux · Linux
Published
2026-05-27
·
Updated
2026-05-27
·
CVE-2026-45891
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
net: hns3: fix double free issue for tx spare buffer
In hns3 set ringparam(), a temporary copy (tmp rings) of the ring structure
is created for rollback. However, the tx spare pointer in the original
ring handle is incorrectly left pointing to the old backup memory.
Later, if memory allocation fails in hns3 init all ring() during the setup,
the error path attempts to free all newly allocated rings. Since tx spare
contains a stale (non-NULL) pointer from the backup, it is mistaken for
a newly allocated buffer and is erroneously freed, leading to a double-free
of the backup memory.
The root cause is that the tx spare field was not cleared after its value
was saved in tmp rings, leaving a dangling pointer.
Fix this by setting tx spare to NULL in the original ring structure
when the creation of the new
tx spare fails. This ensures the
error cleanup path only frees genuinely newly allocated buffers. Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux