CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2024-50244 – fs/ntfs3: Additional check in ni_clear()
https://notcve.org/view.php?id=CVE-2024-50244
09 Nov 2024 — 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. 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 •
CVSS: 5.5EPSS: 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
09 Nov 2024 — 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. 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 •
CVSS: 7.8EPSS: 0%CPEs: 4EXPL: 0CVE-2024-50242 – fs/ntfs3: Additional check in ntfs_file_release
https://notcve.org/view.php?id=CVE-2024-50242
09 Nov 2024 — 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 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2024-50241 – NFSD: Initialize struct nfsd4_copy earlier
https://notcve.org/view.php?id=CVE-2024-50241
09 Nov 2024 — In the Linux kernel, the following vulnerability has been resolved: NFSD: Initialize struct nfsd4_copy earlier Ensure the refcount and async_copies fields are initialized early. cleanup_async_copy() will reference these fields if an error occurs in nfsd4_copy(). If they are not correctly initialized, at the very least, a refcount underflow occurs. In the Linux kernel, the following vulnerability has been resolved: NFSD: Initialize struct nfsd4_copy earlier Ensure the refcount and async_copies fields are ini... • https://git.kernel.org/stable/c/6a488ad7745b8f64625c6d3a24ce7e448e83f11b •
CVSS: 5.5EPSS: 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
09 Nov 2024 — 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 current... • https://git.kernel.org/stable/c/413db06c05e729639e9b64cf7ab5d918b8182006 •
CVSS: 5.5EPSS: 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
09 Nov 2024 — 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 dat... • https://git.kernel.org/stable/c/e464a3180a43b6596bd267f9f274e1793bfb8150 •
CVSS: 5.5EPSS: 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
09 Nov 2024 — 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 initialisa... • https://git.kernel.org/stable/c/19281571a4d5b6049dad9318db081af48818b1d2 •
CVSS: 7.1EPSS: 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
09 Nov 2024 — 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 •
CVSS: 5.5EPSS: 0%CPEs: 9EXPL: 0CVE-2024-50236 – wifi: ath10k: Fix memory leak in management tx
https://notcve.org/view.php?id=CVE-2024-50236
09 Nov 2024 — In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Fix memory leak in management tx In the current logic, memory is allocated for storing the MSDU context during management packet TX but this memory is not being freed during management TX completion. Similar leaks are seen in the management TX cleanup logic. Kmemleak reports this problem as below, unreferenced object 0xffffff80b64ed250 (size 16): comm "kworker/u16:7", pid 148, jiffies 4294687130 (age 714.199s) hex dump (first ... • https://git.kernel.org/stable/c/dc405152bb64d4ae01c9ac669de25b2d1fb6fc2d •
CVSS: 7.8EPSS: 0%CPEs: 5EXPL: 0CVE-2024-50235 – wifi: cfg80211: clear wdev->cqm_config pointer on free
https://notcve.org/view.php?id=CVE-2024-50235
09 Nov 2024 — In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear wdev->cqm_config pointer on free When we free wdev->cqm_config when unregistering, we also need to clear out the pointer since the same wdev/netdev may get re-registered in another network namespace, then destroyed later, running this code again, which results in a double-free. In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: clear wdev->cqm_config pointer on free When we free wdev->c... • https://git.kernel.org/stable/c/c797498e860e9a435a651bbf0789433684ce6dd8 •