Поиск уязвимостей
Количество 18
Количество 18
CVE-2023-53087
In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the ...
CVE-2023-53087
In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the ...
CVE-2023-53087
In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the
CVE-2023-53087
In the Linux kernel, the following vulnerability has been resolved: d ...
ROS-20260128-73-0052
Уязвимость kernel-lt
GHSA-5w85-r73p-4mf2
In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs ...
ALT-PU-2023-8722
ALT-PU-2023-8722: package `kernel-image-rt` update to version 5.10.176-alt1.rt86
ALT-PU-2023-8588
ALT-PU-2023-8588: package `kernel-image-rt` update to version 5.10.176-alt1.rt86
ALT-PU-2023-8792
ALT-PU-2023-8792: package `kernel-image-std-def` update to version 5.15.104-alt1
ALT-PU-2023-8581
ALT-PU-2023-8581: package `kernel-image-std-def` update to version 5.10.176-alt1
ALT-PU-2023-8557
ALT-PU-2023-8557: package `kernel-image-un-def` update to version 5.15.104-alt1
SUSE-SU-2025:02262-1
Security update for the Linux Kernel
ALT-PU-2023-8682
ALT-PU-2023-8682: package `kernel-image-std-kvm` update to version 5.10.176-alt1
SUSE-SU-2025:02173-1
Security update for the Linux Kernel
ALT-PU-2023-1495
ALT-PU-2023-1495: package `kernel-image-mp` update to version 6.2.8-alt1
ALT-PU-2023-8867
ALT-PU-2023-8867: package `kernel-image-un-def` update to version 6.1.21-alt1
ALT-PU-2024-4843
ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1
ALT-PU-2024-4263
ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-53087 In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-53087 In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-53087 In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs the | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-53087 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260128-73-0052 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
GHSA-5w85-r73p-4mf2 In the Linux kernel, the following vulnerability has been resolved: drm/i915/active: Fix misuse of non-idle barriers as fence trackers Users reported oopses on list corruptions when using i915 perf with a number of concurrently running graphics applications. Root cause analysis pointed at an issue in barrier processing code -- a race among perf open / close replacing active barriers with perf requests on kernel context and concurrent barrier preallocate / acquire operations performed during user context first pin / last unpin. When adding a request to a composite tracker, we try to reuse an existing fence tracker, already allocated and registered with that composite. The tracker we obtain may already track another fence, may be an idle barrier, or an active barrier. If the tracker we get occurs a non-idle barrier then we try to delete that barrier from a list of barrier tasks it belongs to. However, while doing that we don't respect return value from a function that performs ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ALT-PU-2023-8722 ALT-PU-2023-8722: package `kernel-image-rt` update to version 5.10.176-alt1.rt86 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8588 ALT-PU-2023-8588: package `kernel-image-rt` update to version 5.10.176-alt1.rt86 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8792 ALT-PU-2023-8792: package `kernel-image-std-def` update to version 5.15.104-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8581 ALT-PU-2023-8581: package `kernel-image-std-def` update to version 5.10.176-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8557 ALT-PU-2023-8557: package `kernel-image-un-def` update to version 5.15.104-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
SUSE-SU-2025:02262-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-8682 ALT-PU-2023-8682: package `kernel-image-std-kvm` update to version 5.10.176-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
SUSE-SU-2025:02173-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-1495 ALT-PU-2023-1495: package `kernel-image-mp` update to version 6.2.8-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2023-8867 ALT-PU-2023-8867: package `kernel-image-un-def` update to version 6.1.21-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
ALT-PU-2024-4843 ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад | ||
ALT-PU-2024-4263 ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад |
Уязвимостей на страницу