CVE-2025-38301

{"id": "CVE-2025-38301", "cveTags": [], "metrics": {}, "published": "2025-07-10T08:15:28.860", "references": [{"url": "https://git.kernel.org/stable/c/3728101f56ef54425a11027a3ddc2c3941d60b71", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/c8bb1bcea877446f86922a8fd1661b8c07d90e5c", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/fe8abdd175d7b547ae1a612757e7902bcd62e9cf", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvmem: zynqmp_nvmem: unbreak driver after cleanup\n\nCommit 29be47fcd6a0 (\"nvmem: zynqmp_nvmem: zynqmp_nvmem_probe cleanup\")\nchanged the driver to expect the device pointer to be passed as the\n\"context\", but in nvmem the context parameter comes from nvmem_config.priv\nwhich is never set - Leading to null pointer exceptions when the device is\naccessed."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: nvmem: zynqmp_nvmem: unbreak driver after cleanup El commit 29be47fcd6a0 (\"nvmem: zynqmp_nvmem: zynqmp_nvmem_probe cleanup\") cambi\u00f3 el controlador para esperar que el puntero del dispositivo se pase como \"contexto\", pero en nvmem el par\u00e1metro de contexto proviene de nvmem_config.priv que nunca se establece, lo que genera excepciones de puntero nulo cuando se accede al dispositivo."}], "lastModified": "2025-07-10T13:17:30.017", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}