Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Поиск уязвимостей

Количество 16

Количество 16

ubuntu логотип

CVE-2022-48950

около 2 лет назад

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
EPSS: Низкий
redhat логотип

CVE-2022-48950

около 2 лет назад

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 6.7
EPSS: Низкий
nvd логотип

CVE-2022-48950

около 2 лет назад

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
EPSS: Низкий
debian логотип

CVE-2022-48950

около 2 лет назад

In the Linux kernel, the following vulnerability has been resolved: p ...

CVSS3: 7.8
EPSS: Низкий
github логотип

GHSA-qw38-ppmm-fjpw

около 2 лет назад

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
EPSS: Низкий
fstec логотип

BDU:2024-09780

почти 4 года назад

Уязвимость функции perf_pending_task() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации

CVSS3: 7.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-7840

почти 4 года назад

ALT-PU-2022-7840: package `kernel-image-un-def` update to version 6.0.14-alt1

CVSS3: 7.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-3368

почти 4 года назад

ALT-PU-2022-3368: package `kernel-image-std-def` update to version 5.15.84-alt1

CVSS3: 7.8
EPSS: Низкий
redos логотип

ROS-20250211-01

больше 1 года назад

Множественные уязвимости kernel-lt

CVSS3: 7.8
EPSS: Низкий
altlinux логотип

ALT-PU-2023-1011

почти 4 года назад

ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1

CVSS3: 8
EPSS: Низкий
altlinux логотип

ALT-PU-2023-1044

почти 4 года назад

ALT-PU-2023-1044: package `kernel-image-un-def` update to version 5.15.87-alt1

CVSS3: 8.8
EPSS: Низкий
altlinux логотип

ALT-PU-2022-3371

почти 4 года назад

ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1

CVSS3: 9.3
EPSS: Низкий
altlinux логотип

ALT-PU-2022-3364

почти 4 года назад

ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1

CVSS3: 9.3
EPSS: Низкий
altlinux логотип

ALT-PU-2023-7682

почти 3 года назад

ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2

CVSS3: 9.3
EPSS: Низкий
altlinux логотип

ALT-PU-2023-7007

около 3 лет назад

ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1

CVSS3: 9.3
EPSS: Низкий
altlinux логотип

ALT-PU-2023-1814

больше 3 лет назад

ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10

CVSS3: 9.8
EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
ubuntu логотип
CVE-2022-48950

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
0%
Низкий
около 2 лет назад
redhat логотип
CVE-2022-48950

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 6.7
0%
Низкий
около 2 лет назад
nvd логотип
CVE-2022-48950

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
0%
Низкий
около 2 лет назад
debian логотип
CVE-2022-48950

In the Linux kernel, the following vulnerability has been resolved: p ...

CVSS3: 7.8
0%
Низкий
около 2 лет назад
github логотип
GHSA-qw38-ppmm-fjpw

In the Linux kernel, the following vulnerability has been resolved: perf: Fix perf_pending_task() UaF Per syzbot it is possible for perf_pending_task() to run after the event is free()'d. There are two related but distinct cases: - the task_work was already queued before destroying the event; - destroying the event itself queues the task_work. The first cannot be solved using task_work_cancel() since perf_release() itself might be called from a task_work (____fput), which means the current->task_works list is already empty and task_work_cancel() won't be able to find the perf_pending_task() entry. The simplest alternative is extending the perf_event lifetime to cover the task_work. The second is just silly, queueing a task_work while you know the event is going away makes no sense and is easily avoided by re-arranging how the event is marked STATE_DEAD and ensuring it goes through STATE_OFF on the way down.

CVSS3: 7.8
0%
Низкий
около 2 лет назад
fstec логотип
BDU:2024-09780

Уязвимость функции perf_pending_task() ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации

CVSS3: 7.8
0%
Низкий
почти 4 года назад
altlinux логотип
ALT-PU-2022-7840

ALT-PU-2022-7840: package `kernel-image-un-def` update to version 6.0.14-alt1

CVSS3: 7.8
почти 4 года назад
altlinux логотип
ALT-PU-2022-3368

ALT-PU-2022-3368: package `kernel-image-std-def` update to version 5.15.84-alt1

CVSS3: 7.8
почти 4 года назад
redos логотип
ROS-20250211-01

Множественные уязвимости kernel-lt

CVSS3: 7.8
больше 1 года назад
altlinux логотип
ALT-PU-2023-1011

ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1

CVSS3: 8
почти 4 года назад
altlinux логотип
ALT-PU-2023-1044

ALT-PU-2023-1044: package `kernel-image-un-def` update to version 5.15.87-alt1

CVSS3: 8.8
почти 4 года назад
altlinux логотип
ALT-PU-2022-3371

ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1

CVSS3: 9.3
почти 4 года назад
altlinux логотип
ALT-PU-2022-3364

ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1

CVSS3: 9.3
почти 4 года назад
altlinux логотип
ALT-PU-2023-7682

ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2

CVSS3: 9.3
почти 3 года назад
altlinux логотип
ALT-PU-2023-7007

ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1

CVSS3: 9.3
около 3 лет назад
altlinux логотип
ALT-PU-2023-1814

ALT-PU-2023-1814: package `kernel-image-rt` update to version 6.1.28-alt1.rt10

CVSS3: 9.8
больше 3 лет назад

Уязвимостей на страницу