Поиск уязвимостей
Количество 17
Количество 17
GHSA-24j6-88m8-2wx3
In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid:...
CVE-2022-50491
In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 330, name: perf-e...
CVE-2022-50491
In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 330, name: perf-e...
CVE-2022-50491
In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 33
CVE-2022-50491
In the Linux kernel, the following vulnerability has been resolved: c ...
ALT-PU-2022-7815
ALT-PU-2022-7815: package `kernel-image-std-def` update to version 5.15.77-alt1
ALT-PU-2022-7705
ALT-PU-2022-7705: package `kernel-image-un-def` update to version 5.15.77-alt1
ALT-PU-2022-2993
ALT-PU-2022-2993: package `kernel-image-un-def` update to version 6.0.7-alt1
ALT-PU-2022-3094
ALT-PU-2022-3094: package `kernel-image-std-def` update to version 5.10.154-alt1
ALT-PU-2022-3060
ALT-PU-2022-3060: package `kernel-image-mp` update to version 6.0.8-alt1
ALT-PU-2022-3061
ALT-PU-2022-3061: package `kernel-image-std-kvm` update to version 5.10.154-alt1
ALT-PU-2022-3311
ALT-PU-2022-3311: package `kernel-image-rt` update to version 5.10.158-alt1.rt77
ALT-PU-2022-3310
ALT-PU-2022-3310: package `kernel-image-rt` update to version 5.10.158-alt1.rt77
ALT-PU-2022-3371
ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1
ALT-PU-2022-3364
ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1
ALT-PU-2023-7682
ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2
ALT-PU-2023-7007
ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
GHSA-24j6-88m8-2wx3 In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid:... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50491 In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 330, name: perf-e... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50491 In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 330, name: perf-e... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50491 In the Linux kernel, the following vulnerability has been resolved: coresight: cti: Fix hang in cti_disable_hw() cti_enable_hw() and cti_disable_hw() are called from an atomic context so shouldn't use runtime PM because it can result in a sleep when communicating with firmware. Since commit 3c6656337852 ("Revert "firmware: arm_scmi: Add clock management to the SCMI power domain""), this causes a hang on Juno when running the Perf Coresight tests or running this command: perf record -e cs_etm//u -- ls This was also missed until the revert commit because pm_runtime_put() was called with the wrong device until commit 692c9a499b28 ("coresight: cti: Correct the parameter for pm_runtime_put") With lock and scheduler debugging enabled the following is output: coresight cti_sys0: cti_enable_hw -- dev:cti_sys0 parent: 20020000.cti BUG: sleeping function called from invalid context at drivers/base/power/runtime.c:1151 in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 33 | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
CVE-2022-50491 In the Linux kernel, the following vulnerability has been resolved: c ... | CVSS3: 5.5 | 0% Низкий | около 1 года назад | |
ALT-PU-2022-7815 ALT-PU-2022-7815: package `kernel-image-std-def` update to version 5.15.77-alt1 | CVSS3: 7.8 | около 4 лет назад | ||
ALT-PU-2022-7705 ALT-PU-2022-7705: package `kernel-image-un-def` update to version 5.15.77-alt1 | CVSS3: 7.8 | около 4 лет назад | ||
ALT-PU-2022-2993 ALT-PU-2022-2993: package `kernel-image-un-def` update to version 6.0.7-alt1 | CVSS3: 7.8 | около 4 лет назад | ||
ALT-PU-2022-3094 ALT-PU-2022-3094: package `kernel-image-std-def` update to version 5.10.154-alt1 | CVSS3: 8.8 | около 4 лет назад | ||
ALT-PU-2022-3060 ALT-PU-2022-3060: package `kernel-image-mp` update to version 6.0.8-alt1 | CVSS3: 8.8 | около 4 лет назад | ||
ALT-PU-2022-3061 ALT-PU-2022-3061: package `kernel-image-std-kvm` update to version 5.10.154-alt1 | CVSS3: 8.8 | около 4 лет назад | ||
ALT-PU-2022-3311 ALT-PU-2022-3311: package `kernel-image-rt` update to version 5.10.158-alt1.rt77 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2022-3310 ALT-PU-2022-3310: package `kernel-image-rt` update to version 5.10.158-alt1.rt77 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2022-3371 ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2022-3364 ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2023-7682 ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2 | CVSS3: 9.3 | почти 3 года назад | ||
ALT-PU-2023-7007 ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1 | CVSS3: 9.3 | около 3 лет назад |
Уязвимостей на страницу