This task is identified by as the content contains sensitive information such as code security bugs, privacy leaks, etc., so it is only accessible to contributors of this repository.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
Inthe Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In theLinux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")'moved the pmic_glink client listunder a spinlock, as itis accessed by the rpmsg/glink callback,which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to getGLINK to invoke its callbacks in a sleepable context,butuntil then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck toavoid the resulting NULLpointer dereference.This does however result in the userbeing informedabout thiserrorbythe followingentry in the kernellog: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSIwrite request:-5TheLinux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
Inthe Linuxkernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' movedthe pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, whichin turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINKto invoke its callbacks in a sleepable context,but untilthen lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a checkto avoidthe resulting NULLpointer dereference.This does however result in the user beinginformed aboutthis errorbythefollowing entryin the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI writerequest: -5TheLinuxkernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting asleepable context. An effort isunder way to get GLINK to invoke its callbacks in asleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with acheck to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list undera spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expectinga sleepable context. An effort isunder way to get GLINK to invoke its callbacks ina sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under aspinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepablecontext. An effort isunder way toget GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effectof thisis that ucsi_unregister() can nowhappenafter the remote processor, and thereby the communication link with it, isgone.pmic_glink_send() isamended with a check to avoid the resultingNULLpointer dereference.This does howeverresult in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsipmic_glink.ucsi.0: failedto send UCSIwrite request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
IntheLinuxkernel,thefollowing vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Makeclient-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by therpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way toget GLINK to invoke its callbacksin a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister()can nowhappenafter the remote processor,and thereby the communication link with it, isgone. pmic_glink_send() is amended witha check to avoid theresulting NULLpointer dereference.This doeshowever result in the user being informedabout this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to sendUCSI write request: -5TheLinux kernelCVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit 9329933699b3 ( soc: qcom: pmic_glink: Make client-locknon-sleeping ) moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn t feasible as it s expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5
In the Linux kernel, the following vulnerability has been resolved:usb: typec: ucsi: Move unregister out of atomic sectionCommit '9329933699b3 ("soc: qcom: pmic_glink: Make client-locknon-sleeping")' moved the pmic_glink client list under a spinlock, as itis accessed by the rpmsg/glink callback, which in turn is invoked fromIRQ context.This means that ucsi_unregister() is now called from atomic context,which isn't feasible as it's expecting a sleepable context. An effort isunder way to get GLINK to invoke its callbacks in a sleepable context,but until then lets schedule the unregistration.A side effect of this is that ucsi_unregister() can now happenafter the remote processor, and thereby the communication link with it, isgone. pmic_glink_send() is amended with a check to avoid the resulting NULLpointer dereference.This does however result in the user being informed about this error bythe following entry in the kernel log: ucsi_glink.pmic_glink_ucsi pmic_glink.ucsi.0: failed to send UCSI write request: -5The Linux kernel CVE team has assigned CVE-2024-46691 to this issue.
