Количество 18
Количество 18
GHSA-gww6-qc28-623p
In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under...
CVE-2026-64401
In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under cif...
CVE-2026-64401
In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under cif...
CVE-2026-64401
In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under ci
CVE-2026-64401
smb: client: resolve SWN tcon from live registrations
CVE-2026-64401
In the Linux kernel, the following vulnerability has been resolved: s ...
ROS-20261007-80-0421
Уязвимость kernel-lt
ROS-20261007-73-0422
Уязвимость kernel-lt
ALT-PU-2026-12949
ALT-PU-2026-12949: package `kernel-image-6.12` update to version 6.12.98-alt1
ALT-PU-2026-11926
ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1
ALT-PU-2026-12325
ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1
ALT-PU-2026-11606
ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1
ELSA-2026-500249
ELSA-2026-500249: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2026:4254-1
Security update for the Linux Kernel
SUSE-SU-2026:4120-1
Security update for the Linux Kernel
openSUSE-SU-2026:21910-1
Security update for the Linux Kernel
ELSA-2026-500248
ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-11671
ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-gww6-qc28-623p In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-64401 In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under cif... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-64401 In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under cif... | CVSS3: 7 | 0% Низкий | 3 месяца назад | |
CVE-2026-64401 In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under ci | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-64401 smb: client: resolve SWN tcon from live registrations | 0% Низкий | 3 месяца назад | ||
CVE-2026-64401 In the Linux kernel, the following vulnerability has been resolved: s ... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
ROS-20261007-80-0421 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 20 дней назад | |
ROS-20261007-73-0422 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 20 дней назад | |
ALT-PU-2026-12949 ALT-PU-2026-12949: package `kernel-image-6.12` update to version 6.12.98-alt1 | CVSS3: 8.8 | 3 месяца назад | ||
ALT-PU-2026-11926 ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1 | CVSS3: 9.8 | 2 месяца назад | ||
ALT-PU-2026-12325 ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
ALT-PU-2026-11606 ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1 | CVSS3: 10 | 3 месяца назад | ||
ELSA-2026-500249 ELSA-2026-500249: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад | |||
SUSE-SU-2026:4254-1 Security update for the Linux Kernel | около 1 месяца назад | |||
SUSE-SU-2026:4120-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
openSUSE-SU-2026:21910-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ELSA-2026-500248 ELSA-2026-500248: Unbreakable Enterprise kernel security update (IMPORTANT) | около 2 месяцев назад | |||
ALT-PU-2026-11671 ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1 | CVSS3: 10 | 3 месяца назад |
Уязвимостей на страницу