Поиск уязвимостей
Количество 24
Количество 24
CVE-2024-26996
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> error happe...
CVE-2024-26996
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> error happe...
CVE-2024-26996
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> err
CVE-2024-26996
In the Linux kernel, the following vulnerability has been resolved: u ...
GHSA-2wc3-h48p-9gpq
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> ...
BDU:2024-03641
Уязвимость функций ncm_set_alt() и ncm_disable() в модуле drivers/usb/gadget/function/f_ncm.c драйвера USB gadget ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
ROS-20240927-07
Множественные уязвимости kernel-lt
ALT-PU-2024-18370
ALT-PU-2024-18370: package `kernel-image-std-def` update to version 6.1.88-alt1
ALT-PU-2024-7244
ALT-PU-2024-7244: package `kernel-image-un-def` update to version 6.6.29-alt1
ALT-PU-2024-7242
ALT-PU-2024-7242: package `kernel-image-6.8` update to version 6.8.8-alt1
ALT-PU-2024-18214
ALT-PU-2024-18214: package `kernel-image-pine` update to version 6.6.30-alt1
SUSE-SU-2024:1979-1
Security update for the Linux Kernel
SUSE-SU-2024:2184-1
Security update for the Linux Kernel
SUSE-SU-2024:1983-1
Security update for the Linux Kernel
ALT-PU-2024-17905
ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1
ALT-PU-2024-18118
ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1
ALT-PU-2024-7646
ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30
SUSE-SU-2024:2203-1
Security update for the Linux Kernel
SUSE-SU-2024:2135-1
Security update for the Linux Kernel
SUSE-SU-2024:2019-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26996 In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> error happe... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26996 In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> error happe... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26996 In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> err | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26996 In the Linux kernel, the following vulnerability has been resolved: u ... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
GHSA-2wc3-h48p-9gpq In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_ncm: Fix UAF ncm object at re-bind after usb ep transport error When ncm function is working and then stop usb0 interface for link down, eth_stop() is called. At this piont, accidentally if usb transport error should happen in usb_ep_enable(), 'in_ep' and/or 'out_ep' may not be enabled. After that, ncm_disable() is called to disable for ncm unbind but gether_disconnect() is never called since 'in_ep' is not enabled. As the result, ncm object is released in ncm unbind but 'dev->port_usb' associated to 'ncm->port' is not NULL. And when ncm bind again to recover netdev, ncm object is reallocated but usb0 interface is already associated to previous released ncm object. Therefore, once usb0 interface is up and eth_start_xmit() is called, released ncm object is dereferrenced and it might cause use-after-free memory. [function unlink via configfs] usb0: eth_stop dev->port_usb=ffffff9b179c3200 --> ... | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
BDU:2024-03641 Уязвимость функций ncm_set_alt() и ncm_disable() в модуле drivers/usb/gadget/function/f_ncm.c драйвера USB gadget ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 6.4 | 0% Низкий | больше 2 лет назад | |
ROS-20240927-07 Множественные уязвимости kernel-lt | CVSS3: 9.1 | около 2 лет назад | ||
ALT-PU-2024-18370 ALT-PU-2024-18370: package `kernel-image-std-def` update to version 6.1.88-alt1 | CVSS3: 8.2 | больше 2 лет назад | ||
ALT-PU-2024-7244 ALT-PU-2024-7244: package `kernel-image-un-def` update to version 6.6.29-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-7242 ALT-PU-2024-7242: package `kernel-image-6.8` update to version 6.8.8-alt1 | CVSS3: 8.2 | больше 2 лет назад | ||
ALT-PU-2024-18214 ALT-PU-2024-18214: package `kernel-image-pine` update to version 6.6.30-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:1979-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2184-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1983-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-17905 ALT-PU-2024-17905: package `kernel-image-un-def` update to version 6.1.90-alt1 | CVSS3: 9.1 | больше 1 года назад | ||
ALT-PU-2024-18118 ALT-PU-2024-18118: package `kernel-image-mp` update to version 6.8.8-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
ALT-PU-2024-7646 ALT-PU-2024-7646: package `kernel-image-rt` update to version 6.1.90-alt1.rt30 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:2203-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2135-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2019-1 Security update for the Linux Kernel | больше 2 лет назад |
Уязвимостей на страницу