Количество 22
Количество 22
CVE-2026-31400
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, deq...
CVE-2026-31400
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, deq...
CVE-2026-31400
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, d
CVE-2026-31400
In the Linux kernel, the following vulnerability has been resolved: s ...
GHSA-73jc-99jj-ch5v
In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so...
BDU:2026-05764
Уязвимость компонента sunrpc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20261006-80-0138
Уязвимость kernel-lt
ROS-20261006-73-0137
Уязвимость kernel-lt
SUSE-SU-2026:2068-1
Security update for the Linux Kernel
ALT-PU-2026-6774
ALT-PU-2026-6774: package `kernel-image-6.18` update to version 6.18.20-alt1
SUSE-SU-2026:2217-1
Security update for the Linux Kernel
SUSE-SU-2026:2238-1
Security update for the Linux Kernel
openSUSE-SU-2026:20826-1
Security update for the Linux Kernel
ALT-PU-2026-6748
ALT-PU-2026-6748: package `kernel-image-un-def` update to version 6.1.167-alt1
ALT-PU-2026-7359
ALT-PU-2026-7359: package `kernel-image-std-def` update to version 5.10.253-alt1
ALT-PU-2026-7109
ALT-PU-2026-7109: package `kernel-image-rt` update to version 5.10.254-alt1.rt150
ELSA-2026-50372
ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-7350
ALT-PU-2026-7350: package `kernel-image-pine` update to version 6.18.27-alt1
ALT-PU-2026-6044
ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1
ALT-PU-2026-7006
ALT-PU-2026-7006: package `kernel-image-6.12` update to version 6.12.85-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-31400 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, deq... | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
CVE-2026-31400 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, deq... | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
CVE-2026-31400 In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so, d | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
CVE-2026-31400 In the Linux kernel, the following vulnerability has been resolved: s ... | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
GHSA-73jc-99jj-ch5v In the Linux kernel, the following vulnerability has been resolved: sunrpc: fix cache_request leak in cache_release When a reader's file descriptor is closed while in the middle of reading a cache_request (rp->offset != 0), cache_release() decrements the request's readers count but never checks whether it should free the request. In cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the cache_request is removed from the queue and freed along with its buffer and cache_head reference. cache_release() lacks this cleanup. The only other path that frees requests with readers == 0 is cache_dequeue(), but it runs only when CACHE_PENDING transitions from set to clear. If that transition already happened while readers was still non-zero, cache_dequeue() will have skipped the request, and no subsequent call will clean it up. Add the same cleanup logic from cache_read() to cache_release(): after decrementing readers, check if it reached 0 with CACHE_PENDING clear, and if so... | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад | |
BDU:2026-05764 Уязвимость компонента sunrpc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
ROS-20261006-80-0138 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 20 дней назад | |
ROS-20261006-73-0137 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 20 дней назад | |
SUSE-SU-2026:2068-1 Security update for the Linux Kernel | 5 месяцев назад | |||
ALT-PU-2026-6774 ALT-PU-2026-6774: package `kernel-image-6.18` update to version 6.18.20-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
SUSE-SU-2026:2217-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2026:2238-1 Security update for the Linux Kernel | 4 месяца назад | |||
openSUSE-SU-2026:20826-1 Security update for the Linux Kernel | 5 месяцев назад | |||
ALT-PU-2026-6748 ALT-PU-2026-6748: package `kernel-image-un-def` update to version 6.1.167-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
ALT-PU-2026-7359 ALT-PU-2026-7359: package `kernel-image-std-def` update to version 5.10.253-alt1 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-7109 ALT-PU-2026-7109: package `kernel-image-rt` update to version 5.10.254-alt1.rt150 | CVSS3: 9.8 | 6 месяцев назад | ||
ELSA-2026-50372 ELSA-2026-50372: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад | |||
ALT-PU-2026-7350 ALT-PU-2026-7350: package `kernel-image-pine` update to version 6.18.27-alt1 | CVSS3: 9.8 | 6 месяцев назад | ||
ALT-PU-2026-6044 ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
ALT-PU-2026-7006 ALT-PU-2026-7006: package `kernel-image-6.12` update to version 6.12.85-alt1 | CVSS3: 9.8 | 6 месяцев назад |
Уязвимостей на страницу