CVE Vulnerabilities


Exposure of Resource to Wrong Sphere

Published: Jan 12, 2024 | Modified: Jan 18, 2024
CVSS 3.x
CVSS 2.x

A flaw was found in the blkgs destruction path in block/blk-cgroup.c in the Linux kernel, leading to a cgroup blkio memory leakage problem. When a cgroup is being destroyed, cgroup_rstat_flush() is only called at css_release_work_fn(), which is called when the blkcg reference count reaches 0. This circular dependency will prevent blkcg and some blkgs from being freed after they are made offline. This issue may allow an attacker with a local access to cause system instability, such as an out of memory error.


The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Affected Software

Name Vendor Start Version End Version
Linux_kernel Linux 6.2 *
Linux_kernel Linux 6.4 6.4
Linux_kernel Linux 6.4 6.4
Linux_kernel Linux 6.4 6.4
Linux_kernel Linux 6.4 6.4
Linux_kernel Linux 6.4 6.4
Linux_kernel Linux 6.4 6.4

Extended Description

Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.