lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025022707-CVE-2025-21822-88c0@gregkh> Date: Thu, 27 Feb 2025 12:05:09 -0800 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2025-21822: ptp: vmclock: Set driver data before its usage Description =========== In the Linux kernel, the following vulnerability has been resolved: ptp: vmclock: Set driver data before its usage If vmclock_ptp_register() fails during probing, vmclock_remove() is called to clean up the ptp clock and misc device. It uses dev_get_drvdata() to access the vmclock state. However the driver data is not yet set at this point. Assign the driver data earlier. The Linux kernel CVE team has assigned CVE-2025-21822 to this issue. Affected and fixed versions =========================== Issue introduced in 6.13 with commit 20503272422693d793b84f88bf23fe4e955d3a33 and fixed in 6.13.4 with commit 6dbd8b91a065d1d8001446a28e72cd140f9acef0 Issue introduced in 6.13 with commit 20503272422693d793b84f88bf23fe4e955d3a33 and fixed in 6.14-rc3 with commit f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-21822 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/ptp/ptp_vmclock.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/6dbd8b91a065d1d8001446a28e72cd140f9acef0 https://git.kernel.org/stable/c/f7d07cd4f77d77f366c8ffbb8ba8b61f614e5fce
Powered by blists - more mailing lists