8 matches found
CVE-2024-46691 usb: typec: ucsi: Move unregister out of atomic section
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Move unregister out of atomic section Commit '9329933699b3 "soc: qcom: pmicglink: Make client-lock non-sleeping"' moved the pmicglink client list under a spinlock, as it is accessed by the rpmsg/glink callback,...
CVE-2024-46691
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Move unregister out of atomic section Commit '9329933699b3 "soc: qcom: pmicglink: Make client-lock non-sleeping"' moved the pmicglink client list under a spinlock, as it is accessed by the rpmsg/glink callback,...
CVE-2024-44968
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers...
CVE-2024-44968 tick/broadcast: Move per CPU pointer access into the atomic section
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers...
CVE-2024-44968 tick/broadcast: Move per CPU pointer access into the atomic section
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers...
CVE-2024-44968 tick/broadcast: Move per CPU pointer access into the atomic section
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers...
CVE-2024-44968
The connected Nessus entry for CVE-2024-44968 confirms a Linux kernel tick/broadcast timer regression where per-CPU pointer access was taken in a preemptible region due to compiler behavior. The fix moves the per-CPU pointer retrieval to the actual usage site, which is in a non-preemptible region...
CVE-2024-44968
In the Linux kernel, the following vulnerability has been resolved: tick/broadcast: Move per CPU pointer access into the atomic section The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context. This went unnoticed as compilers...