8 matches found
Astra Linux – Vulnerability in Linux 6.12
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: avoid double-free when failing to DMA-map FW msg The semantics are that the caller of fbnicmbxmapmsg retains ownership of the message in case of an error. All existing callers properly free the allocated memory page...
SUSE CVE-2025-38341
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: avoid double free when failing to DMA-map FW msg The semantics are that caller of fbnicmbxmapmsg retains the ownership of the message on error. All existing callers dutifully free the page...
DEBIAN-CVE-2025-38341
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: avoid double free when failing to DMA-map FW msg The semantics are that caller of fbnicmbxmapmsg retains the ownership of the message on error. All existing callers dutifully free the page...
CVE-2025-38341
CVE-2025-38341 pertains to the Linux kernel fbnic driver. The issue is described as a double-free scenario when DMA-mapping a FW message fails within fbnic_mbx_map_msg(), with the documented behavior that the caller retains ownership of the message on error and the page is freed by existing calle...
CVE-2025-38341 eth: fbnic: avoid double free when failing to DMA-map FW msg
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: avoid double free when failing to DMA-map FW msg The semantics are that caller of fbnicmbxmapmsg retains the ownership of the message on error. All existing callers dutifully free the page...
CVE-2025-38341
In the Linux kernel, the following vulnerability has been resolved: eth: fbnic: avoid double free when failing to DMA-map FW msg The semantics are that caller of fbnicmbxmapmsg retains the ownership of the message on error. All existing callers dutifully free the page...
kernel: bnxt_en: Adjust logging of firmware messages in case of released token in __hwrm_send()
In the Linux kernel, the following vulnerability has been resolved: bnxten: Adjust logging of firmware messages in case of released token in hwrmsend In case of token is released due to token-state == BNXTHWRMDEFERRED, released token set to NULL is used in log messages. This issue is expected to ...
CVE-2024-40919
CVE-2024-40919 discusses a Linux kernel bnxt_en issue where a released token (token->state == BNXT_HWRM_DEFERRED) could be logged while the token pointer had already been NULL, risking a NULL pointer dereference. The fix implemented is to add a token pointer check before using the token in log...