Koichiro Den

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A memory leak and cleanup issue has been identified in the Linux kernel when a virtuser device is created via configfs and the probe fails due to an incorrect lookup table. The table is not removed, preventing subsequent probe attempts from succeeding. Additionally, a consistent memory leak in `lookup table->dev id` was spotted using kmemleak. The issue is resolved by introducing `gpio virtuser remove lookup table()` to ensure proper cleanup. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 6.12.0 **Description** A vulnerability in the Linux kernel has been resolved, related to the `virtio net` module. When `virtnet close` is followed by `virtnet open`, some TX completions can remain unconsumed, leading to a crash. The issue can be reproduced under heavy network TX load. The `netdev tx reset queue()` function can be dropped from the `virtnet open` path, and users can still reset `stall max` via sysfs. **Recommendations** To resolve the issue, update the Linux kernel to a version that includes the fix for this vulnerability. Specifically, for versions prior to 6.12.0, apply the patch that adds `netdev tx reset queue()` to the freeze/restore path, immediately after `free unused bufs()`. As a temporary workaround, consider disabling the `virtnet open()` function until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to the use of memory after it has been freed in the iopt area split() function of the iommufd component, due to incorrect control of resource identifiers. This can allow a remote attacker to impact the integrity and availability of protected information. The problem occurs when the original iopt area has filled a domain and is linked to domains itree, and pages nodes are not properly reinserted, causing domains itree to become corrupted and resulting in a use-after-free (UAF) condition. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.