CVE-2025-38552

{"id": "CVE-2025-38552", "cveTags": [], "metrics": {}, "published": "2025-08-16T12:15:31.400", "references": [{"url": "https://git.kernel.org/stable/c/659da22dee5ff316ba63bdaeeac7b58b5442f6c2", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/7c96d519ee15a130842a6513530b4d20acd2bfcd", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/def5b7b2643ebba696fc60ddf675dca13f073486", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/f81b6fbe13c7fc413b5158cdffc6a59391a2a8db", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: plug races between subflow fail and subflow creation\n\nWe have races similar to the one addressed by the previous patch between\nsubflow failing and additional subflow creation. They are just harder to\ntrigger.\n\nThe solution is similar. Use a separate flag to track the condition\n'socket state prevent any additional subflow creation' protected by the\nfallback lock.\n\nThe socket fallback makes such flag true, and also receiving or sending\nan MP_FAIL option.\n\nThe field 'allow_infinite_fallback' is now always touched under the\nrelevant lock, we can drop the ONCE annotation on write."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: conecta las ejecuciones entre el fallo y la creaci\u00f3n de un subflujo. Tenemos ejecuciones similares a la solucionada por el parche anterior entre el fallo de un subflujo y la creaci\u00f3n de subflujos adicionales. Simplemente son m\u00e1s dif\u00edciles de activar. La soluci\u00f3n es similar: se utiliza un indicador independiente para rastrear la condici\u00f3n \u00abEl estado del socket impide la creaci\u00f3n de subflujos adicionales\u00bb, protegida por el bloqueo de reserva. El bloqueo de reserva del socket hace que dicho indicador sea verdadero, y tambi\u00e9n se recibe o env\u00eda una opci\u00f3n MP_FAIL. El campo \u00aballow_infinite_fallback\u00bb ahora siempre se activa bajo el bloqueo correspondiente; podemos omitir la anotaci\u00f3n ONCE al escribir."}], "lastModified": "2025-08-18T20:16:28.750", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}