Поиск уязвимостей
Количество 27
Количество 27
CVE-2022-48988
In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the ...
CVE-2022-48988
In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the ...
CVE-2022-48988
In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the
CVE-2022-48988
In the Linux kernel, the following vulnerability has been resolved: m ...
GHSA-9593-f5wq-r2vm
In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix ...
BDU:2024-10099
Уязвимость функции memcg_write_event_control() подсистемы управления памятью ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
SUSE-SU-2024:4103-1
Security update for the Linux Kernel
SUSE-SU-2024:4140-1
Security update for the Linux Kernel
ALT-PU-2022-7818
ALT-PU-2022-7818: package `kernel-image-std-def` update to version 5.15.83-alt1
ALT-PU-2023-1065
ALT-PU-2023-1065: package `kernel-image-rt` update to version 5.10.162-alt1.rt78
ALT-PU-2023-1061
ALT-PU-2023-1061: package `kernel-image-rt` update to version 5.10.162-alt1.rt78
ROS-20250211-01
Множественные уязвимости kernel-lt
ALT-PU-2022-7839
ALT-PU-2022-7839: package `kernel-image-un-def` update to version 6.0.13-alt1
SUSE-SU-2024:4131-1
Security update for the Linux Kernel
SUSE-SU-2025:0034-1
Security update for the Linux Kernel
SUSE-SU-2024:4100-1
Security update for the Linux Kernel
SUSE-SU-2024:3983-1
Security update for the Linux Kernel
SUSE-SU-2024:3985-1
Security update for the Linux Kernel
ALT-PU-2023-1059
ALT-PU-2023-1059: package `kernel-image-std-kvm` update to version 5.10.163-alt1
ALT-PU-2023-1011
ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48988 In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the ... | CVSS3: 7 | 0% Низкий | около 2 лет назад | |
CVE-2022-48988 In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the ... | CVSS3: 7 | 0% Низкий | около 2 лет назад | |
CVE-2022-48988 In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix the | CVSS3: 7 | 0% Низкий | около 2 лет назад | |
CVE-2022-48988 In the Linux kernel, the following vulnerability has been resolved: m ... | CVSS3: 7 | 0% Низкий | около 2 лет назад | |
GHSA-9593-f5wq-r2vm In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't be renamed, it's safe to access d_name as long as the specified file is a regular cgroup file. Also, as these cgroup interface files can't be removed before the directory, it's safe to access the parent too. Prior to 347c4a874710 ("memcg: remove cgroup_event->cft"), there was a call to __file_cft() which verified that the specified file is a regular cgroupfs file before further accesses. The cftype pointer returned from __file_cft() was no longer necessary and the commit inadvertently dropped the file type check with it allowing any file to slip through. With the invarients broken, the d_name and parent accesses can now race against renames and removals of arbitrary files and cause use-after-free's. Fix ... | CVSS3: 7 | 0% Низкий | около 2 лет назад | |
BDU:2024-10099 Уязвимость функции memcg_write_event_control() подсистемы управления памятью ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7 | 0% Низкий | почти 4 года назад | |
SUSE-SU-2024:4103-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4140-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2022-7818 ALT-PU-2022-7818: package `kernel-image-std-def` update to version 5.15.83-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1065 ALT-PU-2023-1065: package `kernel-image-rt` update to version 5.10.162-alt1.rt78 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1061 ALT-PU-2023-1061: package `kernel-image-rt` update to version 5.10.162-alt1.rt78 | CVSS3: 7.8 | почти 4 года назад | ||
ROS-20250211-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2022-7839 ALT-PU-2022-7839: package `kernel-image-un-def` update to version 6.0.13-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
SUSE-SU-2024:4131-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2025:0034-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4100-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3983-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3985-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2023-1059 ALT-PU-2023-1059: package `kernel-image-std-kvm` update to version 5.10.163-alt1 | CVSS3: 8.4 | почти 4 года назад | ||
ALT-PU-2023-1011 ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1 | CVSS3: 8 | почти 4 года назад |
Уязвимостей на страницу