CVE-2022-48816

{"id": "CVE-2022-48816", "cveTags": [], "metrics": {}, "published": "2024-07-16T12:15:05.687", "references": [{"url": "https://git.kernel.org/stable/c/9482ab4540f5bcc869b44c067ae99b5fca16bd07", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b49ea673e119f59c71645e2f65b3ccad857c90ee", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: lock against ->sock changing during sysfs read\n\n->sock can be set to NULL asynchronously unless ->recv_mutex is held.\nSo it is important to hold that mutex. Otherwise a sysfs read can\ntrigger an oops.\nCommit 17f09d3f619a (\"SUNRPC: Check if the xprt is connected before\nhandling sysfs reads\") appears to attempt to fix this problem, but it\nonly narrows the race window."}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: SUNRPC: bloqueo contra ->cambio de calcet\u00edn durante la lectura de sysfs ->sock se puede establecer en NULL de forma asincr\u00f3nica a menos que se mantenga ->recv_mutex. Por eso es importante mantener ese mutex. De lo contrario, una lectura de sysfs puede provocar un error. El commit 17f09d3f619a (\"SUNRPC: compruebe si el xprt est\u00e1 conectado antes de manejar las lecturas sysfs\") parece intentar solucionar este problema, pero solo reduce la ventana de ejecuci\u00f3n."}], "lastModified": "2024-07-16T13:43:58.773", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}