Количество 42
Количество 42
CVE-2026-43366
In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
CVE-2026-43366
In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
CVE-2026-43366
In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
CVE-2026-43366
In the Linux kernel, the following vulnerability has been resolved: i ...
GHSA-g6hq-4292-hhwx
In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
BDU:2026-12856
Уязвимость компонента io_uring/kbuf.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20261009-80-0547
Уязвимость kernel-lt
ROS-20261009-73-0546
Уязвимость kernel-lt
SUSE-SU-2026:3001-1
Security update for the Linux Kernel (Live Patch 41 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2989-1
Security update for the Linux Kernel (Live Patch 40 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2961-1
Security update for the Linux Kernel (Live Patch 39 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2956-1
Security update for the Linux Kernel (Live Patch 11 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2943-1
Security update for the Linux Kernel (Live Patch 14 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2938-1
Security update for the Linux Kernel (Live Patch 37 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2887-1
Security update for the Linux Kernel (Live Patch 12 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2855-1
Security update for the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise 15 SP7)
SUSE-SU-2026:2933-1
Security update for the Linux Kernel (Live Patch 28 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2899-1
Security update for the Linux Kernel (Live Patch 27 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2890-1
Security update for the Linux Kernel (Live Patch 31 for SUSE Linux Enterprise 15 SP5)
SUSE-SU-2026:2868-1
Security update for the Linux Kernel (Live Patch 30 for SUSE Linux Enterprise 15 SP5)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2026-43366 In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks. | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад |
 | CVE-2026-43366 In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks. | CVSS3: 5.5 | 0% Низкий | 6 месяцев назад |
 | CVE-2026-43366 In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks. | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад |
| CVE-2026-43366 In the Linux kernel, the following vulnerability has been resolved: i ... | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад |
| GHSA-g6hq-4292-hhwx In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks. | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад |
 | BDU:2026-12856 Уязвимость компонента io_uring/kbuf.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.8 | 0% Низкий | 8 месяцев назад |
 | ROS-20261009-80-0547 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 17 дней назад |
| ROS-20261009-73-0546 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 17 дней назад |
 | SUSE-SU-2026:3001-1 Security update for the Linux Kernel (Live Patch 41 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2989-1 Security update for the Linux Kernel (Live Patch 40 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2961-1 Security update for the Linux Kernel (Live Patch 39 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2956-1 Security update for the Linux Kernel (Live Patch 11 for SUSE Linux Enterprise 15 SP7) | 3 месяца назад | ||
| SUSE-SU-2026:2943-1 Security update for the Linux Kernel (Live Patch 14 for SUSE Linux Enterprise 15 SP7) | 3 месяца назад | ||
| SUSE-SU-2026:2938-1 Security update for the Linux Kernel (Live Patch 37 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2887-1 Security update for the Linux Kernel (Live Patch 12 for SUSE Linux Enterprise 15 SP7) | 3 месяца назад | ||
| SUSE-SU-2026:2855-1 Security update for the Linux Kernel RT (Live Patch 11 for SUSE Linux Enterprise 15 SP7) | 4 месяца назад | ||
| SUSE-SU-2026:2933-1 Security update for the Linux Kernel (Live Patch 28 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2899-1 Security update for the Linux Kernel (Live Patch 27 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2890-1 Security update for the Linux Kernel (Live Patch 31 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад | ||
| SUSE-SU-2026:2868-1 Security update for the Linux Kernel (Live Patch 30 for SUSE Linux Enterprise 15 SP5) | 3 месяца назад |
Уязвимостей на страницу