1172 matches found
CVE-2023-53520
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hcisuspendsync crash If hciunregisterdev frees the hcidev object but hcisuspendnotifier may still be accessing it, it can cause the program to crash. Here's the call trace: 102152.653246 Call Trace: 102152.653254...
CVE-2023-53520
The CVE-2023-53520 issue is in the Linux kernel Bluetooth subsystem (hci_suspend_notifier/hci_suspend_sync). The root cause is a race where hci_suspend_notifier may access an hci_dev object after hci_unregister_dev() frees it, causing a crash. The described fix: the patch maintains the reference ...
CVE-2023-53520 Bluetooth: Fix hci_suspend_sync crash
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix hcisuspendsync crash If hciunregisterdev frees the hcidev object but hcisuspendnotifier may still be accessing it, it can cause the program to crash. Here's the call trace: 102152.653246 Call Trace: 102152.653254...
CVE-2023-53518
CVE-2023-53518 — Linux kernel vulnerability fixed: leak in PM / devfreq path during devfreq_dev_release() and resources allocated by srcu_init_notifier_head() must be released via srcu_cleanup_notifier_head(). Connected advisories confirm the issue in the kernel and KMEMLEAK reporting. Exploitati...
CVE-2023-53518 PM / devfreq: Fix leak in devfreq_dev_release()
In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: Fix leak in devfreqdevrelease srcuinitnotifierhead allocates resources that need to be released with a srcucleanupnotifierhead call. Reported by kmemleak...
CVE-2023-53484
CVE-2023-53484 affects the Linux kernel’s cpu_rmap logic. The vulnerability arises in the lib: cpu_rmap path where, if irq_set_affinity_notifier() is called with a NULL notify, the glue pointer in the corresponding rmap->obj array entry is freed but the pointer remains non-null. A subsequent f...
CVE-2023-53484 lib: cpu_rmap: Avoid use after free on rmap->obj array entries
In the Linux kernel, the following vulnerability has been resolved: lib: cpurmap: Avoid use after free on rmap-obj array entries When calling irqsetaffinitynotifier with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the...
CVE-2023-53484 lib: cpu_rmap: Avoid use after free on rmap->obj array entries
In the Linux kernel, the following vulnerability has been resolved: lib: cpurmap: Avoid use after free on rmap-obj array entries When calling irqsetaffinitynotifier with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the...
CVE-2023-53475 usb: xhci: tegra: fix sleep in atomic call
In the Linux kernel, the following vulnerability has been resolved: usb: xhci: tegra: fix sleep in atomic call When we set the dual-role port to Host mode, we observed the following splat: 167.057718 BUG: sleeping function called from invalid context at include/linux/sched/mm.h:229 167.057872...
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 the possibility that hcisuspendnotifier may still access the hcidev object after hciunregisterdev releases...
PT-2025-40191
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel related to the cpu rmap library. Specifically, a use-after-free condition can occur on the rmap-obj array entries. This happens when irq set affinity...
trace/fgraph: Fix the warning caused by missing unregister notifier
...
CVE-2022-50393
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: SDMA update use unlocked iterator SDMA update page table may be called from unlocked context, this generate below warning. Use unlocked iterator to handle this case. WARNING: CPU: 0 PID: 1475 at...
Linux Distros Unpatched Vulnerability : CVE-2025-39829
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback...
SUSE CVE-2025-39829
In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftracesuspendnotifiercall already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:2...
AZL-71209 CVE-2025-39829 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftracesuspendnotifiercall already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:2...
CVE-2025-39829
In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftracesuspendnotifiercall already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:2...
DEBIAN-CVE-2025-39829
In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftracesuspendnotifiercall already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:2...
UBUNTU-CVE-2025-39829
In the Linux kernel, the following vulnerability has been resolved: trace/fgraph: Fix the warning caused by missing unregister notifier This warning was triggered during testing on v6.16: notifier callback ftracesuspendnotifiercall already registered WARNING: CPU: 2 PID: 86 at kernel/notifier.c:2...
CVE-2025-39829
CVE-2025-39829 is a Linux kernel issue in the trace/fgraph path. The vulnerability arises from a notifier that is not unregistered after a failed start_graph_tracing, causing a repeated warning when writing to function_profile_enabled. The connected Nessus entries confirm the concrete details: th...