Lucene search
+L

344 matches found

Vulnrichment
Vulnrichment
•added 2024/10/21 6:02 p.m.•23 views

CVE-2024-49976 tracing/timerlat: Drop interface_lock in stop_kthread()

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Drop interfacelock in stopkthread stopkthread is the offline callback for "trace/osnoise:online", since commit 5bfbcd1ee57b "tracing/timerlat: Add interfacelock around clearing of kthread in stopkthread", the...

6.9AI score0.00178EPSS
SaveExploits0References4
Vulnrichment
Vulnrichment
•added 2024/10/21 6:02 p.m.•17 views

CVE-2024-49953 net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix crash caused by calling xfrmstatedelete twice The km.state is not checked in driver's delayed work. When xfrmstatecheckexpire is called, the state can be reset to XFRMSTATEEXPIRED, even if it is XFRMSTATEDEAD...

6.8AI score0.00303EPSS
SaveExploits0References4
Cvelist
Cvelist
•added 2024/10/21 6:01 p.m.•26 views

CVE-2024-49867 btrfs: wait for fixup workers before stopping cleaner kthread during umount

In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at closectree, we have the following steps in this order: 1 Park the cleaner kthread - this doesn't destroy the kthread, it basically hal...

7.8CVSS0.00299EPSS
SaveExploits0References8
OSV
OSV
•added 2024/10/21 6:01 p.m.•13 views

CVE-2024-49867 btrfs: wait for fixup workers before stopping cleaner kthread during umount

In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at closectree, we have the following steps in this order: 1 Park the cleaner kthread - this doesn't destroy the kthread, it basically hal...

7.8CVSS6.5AI score
SaveExploits0References13
OSV
OSV
•added 2024/10/21 12:15 p.m.•12 views

UBUNTU-CVE-2024-47691

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fsstopgcthread syzbot reports a f2fs bug as below: dumpstack lib/dumpstack.c:88 inline dumpstacklvl+0x241/0x360 lib/dumpstack.c:114 printreport+0xe8/0x550 mm/kasan/report.c:491...

7.8CVSS6.9AI score0.00237EPSS
SaveExploits0References35
CNNVD
CNNVD
•added 2024/10/21 12:00 a.m.•5 views

Linux kernel 安全漏洞

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from an improper wake-up operation on a parked kthread in the kthread subsystem...

5.5CVSS6.6AI score0.00236EPSS
SaveExploits0References7
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/10/21 12:00 a.m.•1 views

CVE-2024-50019: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: kthread: unpark only parked kthread Calling into kthread unparking unconditionally is mostly harmless when the kthread is already unparked. The wake up is then simply ignored because the target is not in TASKPARKED state. However...

5.5CVSS5.8AI score0.00236EPSS
SaveExploits0References1
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/10/21 12:00 a.m.•0 views

CVE-2024-49867: Use After Free

In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at closectree, we have the following steps in this order: 1 Park the cleaner kthread - this doesn't destroy the kthread, it basically hal...

7.8CVSS6.4AI score0.00299EPSS
SaveExploits0References9
SUSE CVE
SUSE CVE
•added 2024/09/28 2:51 a.m.•8 views

SUSE CVE-2024-46845

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

5.5CVSS7.2AI score0.00237EPSS
SaveExploits0References13
NVD
NVD
•added 2024/09/27 1:15 p.m.•18 views

CVE-2024-46845

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

7.8CVSS0.00237EPSS
SaveExploits0References3
OSV
OSV
•added 2024/09/27 1:15 p.m.•7 views

DEBIAN-CVE-2024-46845

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

7.8CVSS5.4AI score0.00237EPSS
SaveExploits0References1
OSV
OSV
•added 2024/09/27 1:15 p.m.•11 views

UBUNTU-CVE-2024-46845

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

7.8CVSS6.4AI score0.00237EPSS
SaveExploits0References11
Cvelist
Cvelist
•added 2024/09/27 12:39 p.m.•39 views

CVE-2024-46845 tracing/timerlat: Only clear timer if a kthread exists

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

7.8CVSS0.00237EPSS
SaveExploits0References3
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/09/27 12:00 a.m.•2 views

CVE-2024-46845: Use After Free

In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a ti...

7.8CVSS5.9AI score0.00237EPSS
SaveExploits0References5
CNNVD
CNNVD
•added 2024/09/27 12:00 a.m.•8 views

Linux kernel 安全漏洞

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel, which stems from a failure to ensure that a kthread remains present when a timer is cleared...

7.8CVSS6.2AI score0.00237EPSS
SaveExploits0References6
SUSE CVE
SUSE CVE
•added 2024/09/19 3:09 a.m.•8 views

SUSE CVE-2024-46788

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Use a cpumask to know what threads are kthreads The startkthread and stopthread code was not always called with the interfacelock held. This means that the kthread variable could be unexpectedly changed causing t...

5.5CVSS7.2AI score0.00214EPSS
SaveExploits0References13
NVD
NVD
•added 2024/09/18 8:15 a.m.•35 views

CVE-2024-46788

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Use a cpumask to know what threads are kthreads The startkthread and stopthread code was not always called with the interfacelock held. This means that the kthread variable could be unexpectedly changed causing t...

7.8CVSS0.00214EPSS
SaveExploits0References3
OSV
OSV
•added 2024/09/18 8:15 a.m.•32 views

UBUNTU-CVE-2024-46788

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Use a cpumask to know what threads are kthreads The startkthread and stopthread code was not always called with the interfacelock held. This means that the kthread variable could be unexpectedly changed causing t...

7.8CVSS6.5AI score0.00214EPSS
SaveExploits0References11
Vulnrichment
Vulnrichment
•added 2024/09/18 7:12 a.m.•17 views

CVE-2024-46788 tracing/osnoise: Use a cpumask to know what threads are kthreads

In the Linux kernel, the following vulnerability has been resolved: tracing/osnoise: Use a cpumask to know what threads are kthreads The startkthread and stopthread code was not always called with the interfacelock held. This means that the kthread variable could be unexpectedly changed causing t...

6.8AI score0.00214EPSS
SaveExploits0References3
CVE
CVE
•added 2024/09/18 7:12 a.m.•129 views

CVE-2024-46788

The CVE-2024-46788 entry concerns a Linux kernel issue in tracing/osnoise: start_kthread() and stop_thread() were not always called with interface_lock held, enabling kthread_stop() to be invoked on a kernel thread (kthread) that should not be stopped, which could trigger OOPS conditions such as ...

7.8CVSS5.2AI score0.00214EPSS
SaveExploits0References3Affected Software1
Rows per page
Query Builder