Поиск уязвимостей
Количество 26
Количество 26
BDU:2025-15680
Уязвимость компонента fs/smb ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260805-80-0004
Уязвимость kernel-lt
ROS-20260805-73-0025
Уязвимость kernel-lt
CVE-2025-39819
In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic als...
CVE-2025-39819
In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic als...
CVE-2025-39819
In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic al
CVE-2025-39819
fs/smb: Fix inconsistent refcnt update
CVE-2025-39819
In the Linux kernel, the following vulnerability has been resolved: f ...
GHSA-96wc-h5c4-3f6j
In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic...
RLSA-2025:19105
Moderate: kernel security update
ELSA-2025-19105
ELSA-2025-19105: kernel security update (MODERATE)
ALT-PU-2025-16600
ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1
ALT-PU-2025-16510
ALT-PU-2025-16510: package `kernel-image-6.12` update to version 6.12.45-alt1
ALT-PU-2025-16465
ALT-PU-2025-16465: package `kernel-image-rt` update to version 6.12.45-alt1
SUSE-SU-2025:4515-1
Security update for the Linux Kernel
SUSE-SU-2025:4521-1
Security update for the Linux Kernel
SUSE-SU-2025:4505-1
Security update for the Linux Kernel
SUSE-SU-2025:4422-1
Security update for the Linux Kernel
SUSE-SU-2025:4516-1
Security update for the Linux Kernel
SUSE-SU-2025:4393-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-15680 Уязвимость компонента fs/smb ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ROS-20260805-80-0004 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
ROS-20260805-73-0025 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 3 месяца назад | |
CVE-2025-39819 In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic als... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2025-39819 In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic als... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2025-39819 In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic al | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2025-39819 fs/smb: Fix inconsistent refcnt update | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2025-39819 In the Linux kernel, the following vulnerability has been resolved: f ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
GHSA-96wc-h5c4-3f6j In the Linux kernel, the following vulnerability has been resolved: fs/smb: Fix inconsistent refcnt update A possible inconsistent update of refcount was identified in `smb2_compound_op`. Such inconsistent update could lead to possible resource leaks. Why it is a possible bug: 1. In the comment section of the function, it clearly states that the reference to `cfile` should be dropped after calling this function. 2. Every control flow path would check and drop the reference to `cfile`, except the patched one. 3. Existing callers would not handle refcount update of `cfile` if -ENOMEM is returned. To fix the bug, an extra goto label "out" is added, to make sure that the cleanup logic would always be respected. As the problem is caused by the allocation failure of `vars`, the cleanup logic between label "finished" and "out" can be safely ignored. According to the definition of function `is_replayable_error`, the error code of "-ENOMEM" is not recoverable. Therefore, the replay logic... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
RLSA-2025:19105 Moderate: kernel security update | около 1 года назад | |||
ELSA-2025-19105 ELSA-2025-19105: kernel security update (MODERATE) | около 1 года назад | |||
ALT-PU-2025-16600 ALT-PU-2025-16600: package `kernel-image-un-def` update to version 6.1.151-alt1 | CVSS3: 9.8 | около 1 года назад | ||
ALT-PU-2025-16510 ALT-PU-2025-16510: package `kernel-image-6.12` update to version 6.12.45-alt1 | CVSS3: 9.8 | около 1 года назад | ||
ALT-PU-2025-16465 ALT-PU-2025-16465: package `kernel-image-rt` update to version 6.12.45-alt1 | CVSS3: 9.8 | около 1 года назад | ||
SUSE-SU-2025:4515-1 Security update for the Linux Kernel | 11 месяцев назад | |||
SUSE-SU-2025:4521-1 Security update for the Linux Kernel | 11 месяцев назад | |||
SUSE-SU-2025:4505-1 Security update for the Linux Kernel | 11 месяцев назад | |||
SUSE-SU-2025:4422-1 Security update for the Linux Kernel | 11 месяцев назад | |||
SUSE-SU-2025:4516-1 Security update for the Linux Kernel | 11 месяцев назад | |||
SUSE-SU-2025:4393-1 Security update for the Linux Kernel | 11 месяцев назад |
Уязвимостей на страницу