Поиск уязвимостей
Количество 19
Количество 19
BDU:2025-16228
Уязвимость функции __extent_writepage() компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20261112-73-0057
Уязвимость kernel-lt
CVE-2023-53429
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context.
CVE-2023-53429
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context.
CVE-2023-53429
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context.
CVE-2023-53429
btrfs: don't check PageError in __extent_writepage
CVE-2023-53429
In the Linux kernel, the following vulnerability has been resolved: b ...
GHSA-95qf-frmh-4g6j
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context.
ALT-PU-2023-8881
ALT-PU-2023-8881: package `kernel-image-un-def` update to version 6.4.7-alt1
ALT-PU-2023-8659
ALT-PU-2023-8659: package `kernel-image-mp` update to version 6.4.8-alt1
ALT-PU-2023-4663
ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1
ALT-PU-2024-6818
ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
SUSE-SU-2025:3751-1
Security update for the Linux Kernel
SUSE-SU-2025:03600-1
Security update for the Linux Kernel
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
SUSE-SU-2025:4141-1
Security update for the Linux Kernel
SUSE-SU-2025:4132-1
Security update for the Linux Kernel
SUSE-SU-2025:4057-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-16228 Уязвимость функции __extent_writepage() компонента btrfs ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20261112-73-0057 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 дней назад | |
CVE-2023-53429 In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context. | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53429 In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context. | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53429 In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context. | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2023-53429 btrfs: don't check PageError in __extent_writepage | CVSS3: 5.5 | 0% Низкий | около 2 месяцев назад | |
CVE-2023-53429 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
GHSA-95qf-frmh-4g6j In the Linux kernel, the following vulnerability has been resolved: btrfs: don't check PageError in __extent_writepage __extent_writepage currenly sets PageError whenever any error happens, and the also checks for PageError to decide if to call error handling. This leads to very unclear responsibility for cleaning up on errors. In the VM and generic writeback helpers the basic idea is that once I/O is fired off all error handling responsibility is delegated to the end I/O handler. But if that end I/O handler sets the PageError bit, and the submitter checks it, the bit could in some cases leak into the submission context for fast enough I/O. Fix this by simply not checking PageError and just using the local ret variable to check for submission errors. This also fundamentally solves the long problem documented in a comment in __extent_writepage by never leaking the error bit into the submission context. | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ALT-PU-2023-8881 ALT-PU-2023-8881: package `kernel-image-un-def` update to version 6.4.7-alt1 | CVSS3: 8 | больше 3 лет назад | ||
ALT-PU-2023-8659 ALT-PU-2023-8659: package `kernel-image-mp` update to version 6.4.8-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
ALT-PU-2023-4663 ALT-PU-2023-4663: package `kernel-image-pine` update to version 6.4.7-alt1 | CVSS3: 9.8 | больше 3 лет назад | ||
ALT-PU-2024-6818 ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | около 2 лет назад | ||
SUSE-SU-2025:3751-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03600-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03634-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4141-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4132-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:4057-1 Security update for the Linux Kernel | около 1 года назад |
Уязвимостей на страницу