CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-50242 – fs/ntfs3: Additional check in ntfs_file_release
https://notcve.org/view.php?id=CVE-2024-50242
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Additional check in ntfs_file_release • https://git.kernel.org/stable/c/550ef40fa6366d5d11b122e5f36b1f9aa20c087e https://git.kernel.org/stable/c/82685eb6ca1db2bd11190451085bcb86ed03aa24 https://git.kernel.org/stable/c/031d6f608290c847ba6378322d0986d08d1a645a •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-50240 – phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
https://notcve.org/view.php?id=CVE-2024-50240
In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usb: fix NULL-deref on runtime suspend Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with this driver. • https://git.kernel.org/stable/c/413db06c05e729639e9b64cf7ab5d918b8182006 https://git.kernel.org/stable/c/370814e9d512ba289612c3780890b80bf2605046 https://git.kernel.org/stable/c/5ebde521fbb9a813b993d4436329a3ca0eeb6574 https://git.kernel.org/stable/c/bd9e4d4a3b127686efc60096271b0a44c3100061 •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-50239 – phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
https://notcve.org/view.php?id=CVE-2024-50239
In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usb-legacy driver. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers. • https://git.kernel.org/stable/c/e464a3180a43b6596bd267f9f274e1793bfb8150 https://git.kernel.org/stable/c/7e8066811a2c43fbb5f53c2c26d389e4bab9da34 https://git.kernel.org/stable/c/b1cffd00daa9cf499b49a0da698eff5032914f6e https://git.kernel.org/stable/c/29240130ab77c80bea1464317ae2a5fd29c16a0c •
CVSS: -EPSS: 0%CPEs: 3EXPL: 0CVE-2024-50238 – phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend
https://notcve.org/view.php?id=CVE-2024-50238
In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usbc driver. Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend. Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers. • https://git.kernel.org/stable/c/19281571a4d5b6049dad9318db081af48818b1d2 https://git.kernel.org/stable/c/bdb35fcff34af08fc7a7cb92f99ff1442e975cb1 https://git.kernel.org/stable/c/c7086dc0539b1b2b61c8c735186698bca4858246 https://git.kernel.org/stable/c/34c21f94fa1e147a19b54b6adf0c93a623b70dd8 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-50237 – wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower
https://notcve.org/view.php?id=CVE-2024-50237
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower Avoid potentially crashing in the driver because of uninitialized private data • https://git.kernel.org/stable/c/5b3dc42b1b0db0264bbbe4ae44c15ab97bfd1e93 https://git.kernel.org/stable/c/b0b862aa3dbcd16b3c4715259a825f48ca540088 https://git.kernel.org/stable/c/78b698fbf37208ee921ee4cedea75b5d33d6ea9f https://git.kernel.org/stable/c/c21efba8b5a86537ccdf43f77536bad02f82776c https://git.kernel.org/stable/c/b2bcbe5450b20641f512d6b26c6b256a5a4f847f https://git.kernel.org/stable/c/8f6cd4d5bb7406656835a90e4f1a2192607f0c21 https://git.kernel.org/stable/c/ee35c423042c9e04079fdee3db545135d609d6ea https://git.kernel.org/stable/c/3ccf525a73d48e814634847f6d4a6150c •