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-2025-68168

In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager initialization in txInit() was not properly initializing TxBlock[0].waitor waitqueue, causing a crash when txEnd(0) is called on read-only filesystems. When a filesystem is mounted read-only, txBegin() returns tid=0 to indicate no transaction. However, txEnd(0) still gets called and tries to access TxBlock[0].waitor via tid_to_tblock(0), but this waitqueue was never initialized because the initialization loop started at index 1 instead of 0. This causes a 'non-static key' lockdep warning and system crash: INFO: trying to register non-static key in txEnd Fix by ensuring all transaction blocks including TxBlock[0] have their waitqueues properly initialized during txInit().

CVE-2025-68168Linux

CVE-2025-68168

In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager initialization in txInit() was not properly initializing TxBlock[0].waitor waitqueue, causing a crash when txEnd(0) is called on read-only filesystems. When a filesystem is mounted read-only, txBegin() returns tid=0 to indicate no transaction. However, txEnd(0) still gets called and tries to access TxBlock[0].waitor via tid_to_tblock(0), but this waitqueue was never initialized because the initialization loop started at index 1 instead of 0. This causes a 'non-static key' lockdep warning and system crash: INFO: trying to register non-static key in txEnd Fix by ensuring all transaction blocks including TxBlock[0] have their waitqueues properly initialized during txInit().

CVSS: -
EPSS: 7.39%
Aktywnie wykorzystywana: brak w KEV
Produkt: -

Co wiadomo

In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager initialization in txInit() was not properly initializing TxBlock[0].waitor waitqueue, causing a crash when txEnd(0) is called on read-only filesystems. When a filesystem is mounted read-only, txBegin() returns tid=0 to indicate no transaction. However, txEnd(0) still gets called and tries to access TxBlock[0].waitor via tid_to_tblock(0), but this waitqueue was never initialized because the initialization loop started at index 1 instead of 0. This causes a 'non-static key' lockdep warning and system crash: INFO: trying to register non-static key in txEnd Fix by ensuring all transaction blocks including TxBlock[0] have their waitqueues properly initialized during txInit().

Źródła

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