Поиск уязвимостей
Количество 24
Количество 24
CVE-2024-57924
In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons ...
CVE-2024-57924
In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons ...
CVE-2024-57924
In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reas
CVE-2024-57924
fs: relax assertions on failure to encode file handles
CVE-2024-57924
In the Linux kernel, the following vulnerability has been resolved: f ...
GHSA-f344-cfpj-cvmx
In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other r...
BDU:2025-15230
Уязвимость функций ovl_encode_real_fh() (fs/overlayfs/copy_up.c) и show_mark_fhandle() (fs/notify/fdinfo.c) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260114-7329
Уязвимость kernel-lt
SUSE-SU-2025:01600-1
Security update for the Linux Kernel
ALT-PU-2025-3500
ALT-PU-2025-3500: package `kernel-image-6.6` update to version 6.6.74-alt1
SUSE-SU-2025:01707-1
Security update for the Linux Kernel
SUSE-SU-2025:01614-1
Security update for the Linux Kernel
ALT-PU-2025-3467
ALT-PU-2025-3467: package `kernel-image-6.12` update to version 6.12.11-alt1
ALT-PU-2025-1980
ALT-PU-2025-1980: package `kernel-image-pine` update to version 6.12.11-alt1
ALT-PU-2025-16600
ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1
SUSE-SU-2025:01951-1
Security update for the Linux Kernel
SUSE-SU-2025:01967-1
Security update for the Linux Kernel
SUSE-SU-2025:01964-1
Security update for the Linux Kernel
ALT-PU-2025-1925
ALT-PU-2025-1925: package `kernel-image-rt` update to version 6.12.11-alt1
SUSE-SU-2025:01919-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-57924 In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons ... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
CVE-2024-57924 In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons ... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
CVE-2024-57924 In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reas | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
CVE-2024-57924 fs: relax assertions on failure to encode file handles | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
CVE-2024-57924 In the Linux kernel, the following vulnerability has been resolved: f ... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
GHSA-f344-cfpj-cvmx In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other r... | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
BDU:2025-15230 Уязвимость функций ovl_encode_real_fh() (fs/overlayfs/copy_up.c) и show_mark_fhandle() (fs/notify/fdinfo.c) ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 2 года назад | |
ROS-20260114-7329 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
SUSE-SU-2025:01600-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-3500 ALT-PU-2025-3500: package `kernel-image-6.6` update to version 6.6.74-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
SUSE-SU-2025:01707-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01614-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-3467 ALT-PU-2025-3467: package `kernel-image-6.12` update to version 6.12.11-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-1980 ALT-PU-2025-1980: package `kernel-image-pine` update to version 6.12.11-alt1 | CVSS3: 7.8 | почти 2 года назад | ||
ALT-PU-2025-16600 ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1 | CVSS3: 9.8 | около 1 года назад | ||
SUSE-SU-2025:01951-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01967-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01964-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-1925 ALT-PU-2025-1925: package `kernel-image-rt` update to version 6.12.11-alt1 | CVSS3: 8 | почти 2 года назад | ||
SUSE-SU-2025:01919-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу