Количество 17
Количество 17
CVE-2026-64218
In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until no more ...
CVE-2026-64218
In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until no more ...
CVE-2026-64218
In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until
CVE-2026-64218
In the Linux kernel, the following vulnerability has been resolved: b ...
ROS-20261014-80-0130
Уязвимость kernel-lt
ROS-20261014-73-0129
Уязвимость kernel-lt
GHSA-jcwg-v5j7-jrrq
In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat unt...
ALT-PU-2026-8600
ALT-PU-2026-8600: package `kernel-image-std-def` update to version 5.10.258-alt1
ALT-PU-2026-8598
ALT-PU-2026-8598: package `kernel-image-un-def` update to version 6.1.175-alt1
ELBA-2026-500163
ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA)
SUSE-SU-2026:4254-1
Security update for the Linux Kernel
SUSE-SU-2026:4120-1
Security update for the Linux Kernel
ALT-PU-2026-8628
ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1
ALT-PU-2026-9890
ALT-PU-2026-9890: package `kernel-image-rpi-un` update to version 6.12.94-alt1
ALT-PU-2026-9892
ALT-PU-2026-9892: package `kernel-image-6.12` update to version 6.12.94-alt1
ALT-PU-2026-11671
ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1
ALT-PU-2026-9924
ALT-PU-2026-9924: package `kernel-image-rpi-un` update to version 6.12.94-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-64218 In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until no more ... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-64218 In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until no more ... | 0% Низкий | 3 месяца назад | ||
CVE-2026-64218 In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat until | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
CVE-2026-64218 In the Linux kernel, the following vulnerability has been resolved: b ... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
ROS-20261014-80-0130 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 11 дней назад | |
ROS-20261014-73-0129 Уязвимость kernel-lt | CVSS3: 7.8 | 0% Низкий | 11 дней назад | |
GHSA-jcwg-v5j7-jrrq In the Linux kernel, the following vulnerability has been resolved: batman-adv: bla: fix report_work leak on backbone_gw purge batadv_bla_purge_backbone_gw() removes stale backbone gateway entries, but fails to properly handle their associated report_work: - If report_work is running, the purge must wait for it to finish before freeing the backbone_gw, otherwise the worker may access freed memory (e.g. bat_priv). - If report_work is pending, the purge must cancel it and release the reference held for that pending work item. The previous implementation called hlist_for_each_entry_safe() inside a spin_lock_bh() section, but cancel_work_sync() may sleep and therefore cannot be called from within a spinlock-protected region. Restructure the loop to handle one entry per spinlock critical section: acquire the lock, find the next entry to purge, remove it from the hash list, then release the lock before calling cancel_work_sync() and dropping the hash_entry reference. Repeat unt... | CVSS3: 7.8 | 0% Низкий | 3 месяца назад | |
ALT-PU-2026-8600 ALT-PU-2026-8600: package `kernel-image-std-def` update to version 5.10.258-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ALT-PU-2026-8598 ALT-PU-2026-8598: package `kernel-image-un-def` update to version 6.1.175-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ELBA-2026-500163 ELBA-2026-500163: Unbreakable Enterprise kernel bug fix update (NA) | 3 месяца назад | |||
SUSE-SU-2026:4254-1 Security update for the Linux Kernel | около 1 месяца назад | |||
SUSE-SU-2026:4120-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
ALT-PU-2026-8628 ALT-PU-2026-8628: package `kernel-image-6.18` update to version 6.18.34-alt1 | CVSS3: 10 | 5 месяцев назад | ||
ALT-PU-2026-9890 ALT-PU-2026-9890: package `kernel-image-rpi-un` update to version 6.12.94-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-9892 ALT-PU-2026-9892: package `kernel-image-6.12` update to version 6.12.94-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-11671 ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1 | CVSS3: 10 | 3 месяца назад | ||
ALT-PU-2026-9924 ALT-PU-2026-9924: package `kernel-image-rpi-un` update to version 6.12.94-alt1 | CVSS3: 10 | 4 месяца назад |
Уязвимостей на страницу