Количество 28
Количество 28
CVE-2026-31402
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting ...
CVE-2026-31402
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting ...
CVE-2026-31402
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting
CVE-2026-31402
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-7xf5-3qmr-j4c6
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflict...
BDU:2026-05258
Уязвимость компонента NFSv4.0 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260527-73-0002
Уязвимость kernel-lt
ELSA-2026-50271
ELSA-2026-50271: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2026-50270
ELSA-2026-50270: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2026-13566
ELSA-2026-13566: kernel security update (IMPORTANT)
ELSA-2026-13565
ELSA-2026-13565: kernel security update (IMPORTANT)
RLSA-2026:13566
Important: kernel security update
RLSA-2026:13565
Important: kernel security update
ELSA-2026-13577
ELSA-2026-13577: kernel security update (IMPORTANT)
RLSA-2026:13577
Important: kernel security update
ELSA-2026-50294
ELSA-2026-50294: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2026-50299
ELSA-2026-50299: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:2317-1
Security update for the Linux Kernel
RLSA-2026:19569
Important: kernel security update
ELSA-2026-50293
ELSA-2026-50293: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-31402 In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting ... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-31402 In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting ... | CVSS3: 7.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-31402 In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-31402 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
GHSA-7xf5-3qmr-j4c6 In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflict... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
BDU:2026-05258 Уязвимость компонента NFSv4.0 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7 | 1% Низкий | 4 месяца назад | |
ROS-20260527-73-0002 Уязвимость kernel-lt | CVSS3: 7 | 1% Низкий | 26 дней назад | |
ELSA-2026-50271 ELSA-2026-50271: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-50270 ELSA-2026-50270: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 месяца назад | |||
ELSA-2026-13566 ELSA-2026-13566: kernel security update (IMPORTANT) | около 2 месяцев назад | |||
ELSA-2026-13565 ELSA-2026-13565: kernel security update (IMPORTANT) | около 2 месяцев назад | |||
RLSA-2026:13566 Important: kernel security update | около 2 месяцев назад | |||
RLSA-2026:13565 Important: kernel security update | около 2 месяцев назад | |||
ELSA-2026-13577 ELSA-2026-13577: kernel security update (IMPORTANT) | около 2 месяцев назад | |||
RLSA-2026:13577 Important: kernel security update | около 2 месяцев назад | |||
ELSA-2026-50294 ELSA-2026-50294: Unbreakable Enterprise kernel security update (IMPORTANT) | 19 дней назад | |||
ELSA-2026-50299 ELSA-2026-50299: Unbreakable Enterprise kernel security update (IMPORTANT) | 19 дней назад | |||
SUSE-SU-2026:2317-1 Security update for the Linux Kernel | 12 дней назад | |||
RLSA-2026:19569 Important: kernel security update | 23 дня назад | |||
ELSA-2026-50293 ELSA-2026-50293: Unbreakable Enterprise kernel security update (IMPORTANT) | 20 дней назад |
Уязвимостей на страницу