drm/amdkfd: svm range restore work deadlock when process exit

...

SUSE CVE-2025-39976

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

CVE-2025-39976

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

EUVD-2022-55090

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: svm range restore work deadlock when process exit kfdprocessnotifierrelease flush svmrangerestorework which calls svmrangelistlockandflushwork to flush deferredlist work, but if deferredlist work mmput release the las...

EUVD-2025-34596

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

CVE-2025-39976

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

UBUNTU-CVE-2025-39976

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

CVE-2025-39976

The CVE-2025-39976 issue concerns the Linux kernel futex handling during fork. The root cause was an incorrect exit path from futex_hash_allocate_default(), where copy_process() exited without proper lock state, causing improper unlocking of tasklist_lock and siglock. The corrected exit path uses...

CVE-2025-39976 futex: Use correct exit on failure from futex_hash_allocate_default()

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

CVE-2025-39976 futex: Use correct exit on failure from futex_hash_allocate_default()

In the Linux kernel, the following vulnerability has been resolved: futex: Use correct exit on failure from futexhashallocatedefault copyprocess uses the wrong error exit path from futexhashallocatedefault. After exiting from futexhashallocatedefault, neither tasklistlock nor siglock has been...

Dark Web Roast - September 2025 Edition

Dark Web Roast - September 2025 Edition By Trellix Advanced Research Center · October 14, 2025 Executive Summary September 2025 brought us a delightful buffet of underground incompetence that makes one wonder if cybercriminals are actively competing for the "Most Spectacular Failure" award. From...

What to do when you click on a suspicious link

October is Cybersecurity Awareness Month, and as the tech-savvy friend or family member, people probably come to you for advice. One of the most common questions is: "I clicked a suspicious link. What do I do now?" Don't worry -- panic won't help, but a calm, step-by-step response will. Share thi...

SUSE CVE-2022-50550

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on adddisk failures When a gendisk is successfully initialized but adddisk fails such as when a loop device has invalid number of minor device numbers specified, blkcginitdisk is called during init...

CVE-2022-50550

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on adddisk failures When a gendisk is successfully initialized but adddisk fails such as when a loop device has invalid number of minor device numbers specified, blkcginitdisk is called during init...

CVE-2022-50538

In the Linux kernel, the following vulnerability has been resolved: vme: Fix error not catched in fakeinit In fakeinit, rootdeviceregister is possible to fail but it's ignored, which can cause unregistering vmeroot fail when exit. general protection fault, probably for non-canonical address...

CVE-2022-50520

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: Fix PCI device refcount leak in radeonatrmgetbios As comment of pcigetclass says, it returns a pcidevice with its refcount increased and decreased the refcount for the input parameter @from if it is not NULL. If we...

UBUNTU-CVE-2022-50550

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on adddisk failures When a gendisk is successfully initialized but adddisk fails such as when a loop device has invalid number of minor device numbers specified, blkcginitdisk is called during init...

EUVD-2025-32783

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on adddisk failures When a gendisk is successfully initialized but adddisk fails such as when a loop device has invalid number of minor device numbers specified, blkcginitdisk is called during init...

CVE-2022-50550 blk-iolatency: Fix memory leak on add_disk() failures

In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on adddisk failures When a gendisk is successfully initialized but adddisk fails such as when a loop device has invalid number of minor device numbers specified, blkcginitdisk is called during init...

CVE-2022-50538

CVE-2022-50538 pertains to the Linux kernel VME subsystem. In fake_init(), __root_device_register() may fail and the error is not handled, which can cause unregistering vme_root during exit to fail, potentially yielding a general protection fault and a null-ptr-deref (non-canonical address 0xdfff...