Bugzilla – Bug 1219830
VUL-0: CVE-2024-25740: kernel-source,kernel-source-azure,kernel-source-rt: memory leak flaw was found in the UBI driver in ubi_attach()
Last modified: 2024-06-12 11:57:10 UTC
A memory leak flaw was found in the UBI driver in drivers/mtd/ubi/attach.c in the Linux kernel through 6.7.4 for UBI_IOCATT, because kobj->name is not released. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25740 https://lore.kernel.org/lkml/0171b6cc-95ee-3538-913b-65a391a446b3%40huawei.com/T/ https://www.cve.org/CVERecord?id=CVE-2024-25740
No patch merged yet. We have CONFIG_UBIFS_FS=m in: - cve/linux-3.0 - SLE15-SP3-LTSS - cve/linux-5.14 - SLE15-SP6 - stable - master
Sure, So we indeed have CONFIG_UBIFS_FS=m on pretty much every branch, but we also have it marked as unsupported/optional, e.g.: origin/master:supported.conf:- fs/ubifs/ubifs origin/vanilla:supported.conf:- kernel/fs/ubifs/ubifs origin/linux-next:supported.conf:- kernel/fs/ubifs/ubifs origin/stable:supported.conf:- fs/ubifs/ubifs origin/slowroll:supported.conf:- fs/ubifs/ubifs origin/SLE15-SP6-AZURE:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP6:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP6-RT:supported.conf:-!optional fs/ubifs/ubifs origin/ALP-current:supported.conf:-!optional fs/ubifs/ubifs origin/ALP-current-RT:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP5-AZURE:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP5:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP5-RT:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP4-RT:supported.conf:-!optional fs/ubifs/ubifs origin/SLE15-SP3-RT:supported.conf:-!optional fs/ubifs/ubifs which means that the module is only shipped on Leap and on the optional kernel package. I don't think there's anything actionable at the moment, we'll eventually receive whatever upstream does via git-fixes (I sometimes handle those for filesystems unsupported in SLE as best-effort for Leap users, assuming they aren't too intrusive for SLE).
At this moment, I didn't find useful information on google for this CVE-2024-25740.
(In reply to Joey Lee from comment #4) > At this moment, I didn't find useful information on google for this > CVE-2024-25740. There's really nothing further to the lore thread mentioned in comment #0, so there's no reviewed patch yet. But in any case, as per my comment #3, this is extremely low-prio since it is not affecting SLE.
Reassigning back to security, since this isn't affecting SLE at all (comment #3).
All done, closing.