Поиск уязвимостей
Количество 30
Количество 30
BDU:2025-08803
Уязвимость функции atm_dev_deregister() (net/atm/resources.c) операционных систем Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260304-80-0042
Уязвимость kernel-lt
ROS-20260304-73-0032
Уязвимость kernel-lt
CVE-2025-38245
In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainte...
CVE-2025-38245
In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainte...
CVE-2025-38245
In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not ta
CVE-2025-38245
atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().
CVE-2025-38245
In the Linux kernel, the following vulnerability has been resolved: a ...
GHSA-w7f8-76rv-q749
In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not...
ALT-PU-2025-16618
ALT-PU-2025-16618: package `kernel-image-rt` update to version 5.10.240-alt1.rt134
ALT-PU-2025-16605
ALT-PU-2025-16605: package `kernel-image-std-def` update to version 5.10.240-alt1
ALT-PU-2025-16596
ALT-PU-2025-16596: package `kernel-image-un-def` update to version 6.1.144-alt1
ALT-PU-2025-16509
ALT-PU-2025-16509: package `kernel-image-6.12` update to version 6.12.41-alt1
ALT-PU-2025-16464
ALT-PU-2025-16464: package `kernel-image-rt` update to version 6.12.41-alt1
SUSE-SU-2025:03204-1
Security update for the Linux Kernel
ALT-PU-2026-1529
ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1
SUSE-SU-2025:03272-1
Security update for the Linux Kernel
SUSE-SU-2025:03301-1
Security update for the Linux Kernel
SUSE-SU-2025:03382-1
Security update for the Linux Kernel
SUSE-SU-2025:03290-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-08803 Уязвимость функции atm_dev_deregister() (net/atm/resources.c) операционных систем Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260304-80-0042 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
ROS-20260304-73-0032 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 8 месяцев назад | |
CVE-2025-38245 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainte... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2025-38245 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not tainte... | CVSS3: 5.7 | 0% Низкий | больше 1 года назад | |
CVE-2025-38245 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not ta | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
CVE-2025-38245 atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
CVE-2025-38245 In the Linux kernel, the following vulnerability has been resolved: a ... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
GHSA-w7f8-76rv-q749 In the Linux kernel, the following vulnerability has been resolved: atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister(). syzbot reported a warning below during atm_dev_register(). [0] Before creating a new device and procfs/sysfs for it, atm_dev_register() looks up a duplicated device by __atm_dev_lookup(). These operations are done under atm_dev_mutex. However, when removing a device in atm_dev_deregister(), it releases the mutex just after removing the device from the list that __atm_dev_lookup() iterates over. So, there will be a small race window where the device does not exist on the device list but procfs/sysfs are still not removed, triggering the splat. Let's hold the mutex until procfs/sysfs are removed in atm_dev_deregister(). [0]: proc_dir_entry 'atm/atmtcp:0' already registered WARNING: CPU: 0 PID: 5919 at fs/proc/generic.c:377 proc_register+0x455/0x5f0 fs/proc/generic.c:377 Modules linked in: CPU: 0 UID: 0 PID: 5919 Comm: syz-executor284 Not... | CVSS3: 7.8 | 0% Низкий | больше 1 года назад | |
ALT-PU-2025-16618 ALT-PU-2025-16618: package `kernel-image-rt` update to version 5.10.240-alt1.rt134 | CVSS3: 8 | больше 1 года назад | ||
ALT-PU-2025-16605 ALT-PU-2025-16605: package `kernel-image-std-def` update to version 5.10.240-alt1 | CVSS3: 8 | больше 1 года назад | ||
ALT-PU-2025-16596 ALT-PU-2025-16596: package `kernel-image-un-def` update to version 6.1.144-alt1 | CVSS3: 9.3 | больше 1 года назад | ||
ALT-PU-2025-16509 ALT-PU-2025-16509: package `kernel-image-6.12` update to version 6.12.41-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
ALT-PU-2025-16464 ALT-PU-2025-16464: package `kernel-image-rt` update to version 6.12.41-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
SUSE-SU-2025:03204-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2026-1529 ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1 | CVSS3: 9.8 | 10 месяцев назад | ||
SUSE-SU-2025:03272-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03301-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03382-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03290-1 Security update for the Linux Kernel | около 1 года назад |
Уязвимостей на страницу