Yunjian Wang

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a use-after-free vulnerability in the `i40e client subtask()` function. This vulnerability occurs because the object `pf->cinst` is freed by the call to `i40e client del instance`, but `pf->cinst->lan info` is still being accessed after the free. The fix involves adding a missing return to prevent this access. The vulnerability may allow an attacker to cause a denial of service. **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 (affected versions not specified) **Description** A refcount leak issue has been identified in the Linux kernel, specifically in the htb parent to leaf offload function. The commit ae81feb7338c, which aimed to fix a NULL pointer dereference bug, was found to be incorrect. The htb graft helper function properly handles the case when new q is NULL, but skipping this call creates an inconsistency where dev queue->qdisc points to the old qdisc, while cl->parent->leaf.q points to the new one, which can be noop qdisc if new q is NULL. This inconsistency can lead to refcount leaks. The correct fix involves adding a NULL pointer check to protect qdisc refcount inc inside htb parent to leaf offload. **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 (affected versions not specified) **Description** A null pointer dereference issue has been resolved in the Linux kernel. The issue occurs when `alloc pages node()` returns null in `svc rqst alloc()`, causing the null `rq scratch page` pointer to be dereferenced when calling `put page()` in `svc rqst free()`. This is fixed by adding a null check. The issue is related to the SUNRPC component. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.