CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-50245 – fs/ntfs3: Fix possible deadlock in mi_read
https://notcve.org/view.php?id=CVE-2024-50245
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix possible deadlock in mi_read Mutex lock with another subclass used in ni_lock_dir(). • https://git.kernel.org/stable/c/4534a70b7056fd4b9a1c6db5a4ce3c98546b291e https://git.kernel.org/stable/c/47e8a17491e37df53743bc2e72309f8f0d6224af https://git.kernel.org/stable/c/c8e7d3b72ee57e43d58ba560fe7970dd840a4061 https://git.kernel.org/stable/c/34e3220efd666d49965a26840d39f27601ce70f4 https://git.kernel.org/stable/c/f1bc362fe978952a9304bd0286788b0ae7724f14 https://git.kernel.org/stable/c/03b097099eef255fbf85ea6a786ae3c91b11f041 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-50244 – fs/ntfs3: Additional check in ni_clear()
https://notcve.org/view.php?id=CVE-2024-50244
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Additional check in ni_clear() Checking of NTFS_FLAGS_LOG_REPLAYING added to prevent access to uninitialized bitmap during replay process. • https://git.kernel.org/stable/c/4534a70b7056fd4b9a1c6db5a4ce3c98546b291e https://git.kernel.org/stable/c/60fb94ef46c2359dd06cbe30bfc2499f639433df https://git.kernel.org/stable/c/14a23e15a5e8331bb0cf21288723fa530a45b2a4 https://git.kernel.org/stable/c/7a4ace681dbb652aeb40e1b88f9134b880fdeeb5 https://git.kernel.org/stable/c/80824967ec714dda02cd79091aa186bbc16c5cf3 https://git.kernel.org/stable/c/d178944db36b3369b78a08ba520de109b89bf2a9 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-50243 – fs/ntfs3: Fix general protection fault in run_is_mapped_full
https://notcve.org/view.php?id=CVE-2024-50243
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix general protection fault in run_is_mapped_full Fixed deleating of a non-resident attribute in ntfs_create_inode() rollback. • https://git.kernel.org/stable/c/4534a70b7056fd4b9a1c6db5a4ce3c98546b291e https://git.kernel.org/stable/c/509c1c6b499a4d9026b58c6e1c3a10ed8db1839f https://git.kernel.org/stable/c/68b39c0765de7c97b34889c1f5e81c2a223fdacc https://git.kernel.org/stable/c/8e87c9aa8cf92cfceaff0aab244318bbb8b35137 https://git.kernel.org/stable/c/a33fb016e49e37aafab18dc3c8314d6399cb4727 •
CVSS: -EPSS: 0%CPEs: 4EXPL: 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/4534a70b7056fd4b9a1c6db5a4ce3c98546b291e https://git.kernel.org/stable/c/d1ac7e2620302e3e49573df39bd4e868e8b4962a 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 •