Xin Xiong

A reference counting issue in the Linux kernel has been identified, specifically in the atmel nand controller init function. This issue occurs in several error handling paths where the function returns an error code without properly balancing the reference count of the `nc->dmac` object, which was previously increased by `dma request channel()`. This can lead to refcount leaks.

A memory leak issue has been identified in the Linux kernel, specifically in the ksmbd module. The problem occurs when the `id` and `uid` have the same value in the `smb check perm dacl()` function, causing the function to exit the loop without properly decrementing the reference count of the `posix acls` object. This can lead to memory leaks.

Name of the Vulnerable Software and Affected Versions: Linux kernel (affected versions not specified) Description: The issue is related to a reference count leak in the `uniphier spi probe()` function. This occurs when either `dma get slave caps()` or `devm spi register master()` returns an error code, causing the function to forget to decrease the refcount of both `dma rx` and `dma tx` objects. This may lead to refcount leaks. The issue happens in several error paths in `uniphier spi probe()`. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

A reference count leak issue was found in the Linux kernel's NFSv4.2 implementation, specifically in the ` nfs42 proc copy notify()` function. The issue occurs in two error paths where the function returns an error code without properly balancing the reference count of the `ctx` object, which was previously bumped by `get nfs open context()`. This can cause reference count leaks.

A reference count leak occurs in the `amdgpu cs fence to handle ioctl()` function within the AMD GPU driver. The issue is triggered during an error path when the `info->in.what` variable falls into the default case, causing the function to return -EINVAL without decrementing the reference count of a dma fence object previously increased by `amdgpu cs get fence()`. This failure to manage the reference count can lead to memory leaks and may allow an attacker to cause a denial of service.