Używamy niezbędnych plików cookie do działania DataHouse.pl oraz opcjonalnych cookies do analityki i marketingu. Możesz zaakceptować wszystkie, odrzucić opcjonalne albo skonfigurować zgody.

OK, ZGADZAM SIĘ NIE ZGADZAM SIĘ ZMIENIAM ZGODY

Dzięki plikom cookies i podobnym technologiom (zwanym dalej „plikami cookies”) możemy poprawiać funkcjonalność naszej strony oraz wyświetlać treści dopasowane do Twoich potrzeb i oczekiwań.

Więcej informacji na temat wykorzystywania plików cookies znajdziesz w naszej [Polityce plików cookies].

Wyrażam zgodę na:

Analityczne wykorzystywanie plików cookies

Marketingowe wykorzystywanie plików cookies

Wykorzystywanie niezbędnych plików cookies (zawsze aktywne)

Twoje preferencje dotyczące plików cookies, wyrażone po zalogowaniu do serwisu, zostaną przypisane do Twojego konta Datahouse.pl. Dzięki temu zostaną zachowane także wtedy, gdy zalogujesz się na swoje konto z innego urządzenia lub przeglądarki.

POTWIERDŹ WYBÓR ANULUJ

CVE-2024-53084: linux kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Break an object reference loop When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it: PVR GEM Object GPU scheduler "finished" fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop. To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.

CVE-2024-53084CVSS 5.5Linux

CVE-2024-53084: linux kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Break an object reference loop When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it: PVR GEM Object GPU scheduler "finished" fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop. To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.

CVSS: 5.5 MEDIUM
EPSS: 8.39%
Aktywnie wykorzystywana: brak w KEV
Produkt: linux kernel

Co wiadomo

In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Break an object reference loop When remaining resources are being cleaned up on driver close, outstanding VM mappings may result in resources being leaked, due to an object reference loop, as shown below, with each object (or set of objects) referencing the object below it: PVR GEM Object GPU scheduler "finished" fence GPU scheduler “scheduled” fence PVR driver “done” fence PVR Context PVR VM Context PVR VM Mappings PVR GEM Object The reference that the PVR VM Context has on the VM mappings is a soft one, in the sense that the freeing of outstanding VM mappings is done as part of VM context destruction; no reference counts are involved, as is the case for all the other references in the loop. To break the reference loop during cleanup, free the outstanding VM mappings before destroying the PVR Context associated with the VM context.

Źródła

Wróć do centrum bezpieczeństwa Skontaktuj się z DataHouse