CVE-2023-52672

{"id": "CVE-2023-52672", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.0, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.0}]}, "published": "2024-05-17T14:15:10.527", "references": [{"url": "https://git.kernel.org/stable/c/162ae0e78bdabf84ef10c1293c4ed7865cb7d3c8", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/3efbd114b91525bb095b8ae046382197d92126b9", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/68e51bdb1194f11d3452525b99c98aff6f837b24", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/6fb70694f8d1ac34e45246b0ac988f025e1e5b55", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b87a1229d8668fbc78ebd9ca0fc797a76001c60f", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/e95aada4cb93d42e25c30a0ef9eb2923d9711d4a", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-400"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\npipe: wakeup wr_wait after setting max_usage\n\nCommit c73be61cede5 (\"pipe: Add general notification queue support\") a\nregression was introduced that would lock up resized pipes under certain\nconditions. See the reproducer in [1].\n\nThe commit resizing the pipe ring size was moved to a different\nfunction, doing that moved the wakeup for pipe->wr_wait before actually\nraising pipe->max_usage. If a pipe was full before the resize occured it\nwould result in the wakeup never actually triggering pipe_write.\n\nSet @max_usage and @nr_accounted before waking writers if this isn't a\nwatch queue.\n\n[Christian Brauner <brauner@kernel.org>: rewrite to account for watch queues]"}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: tuber\u00eda: despertar wr_wait despu\u00e9s de configurar max_usage Confirmar c73be61cede5 (\"tuber\u00eda: Agregar soporte de cola de notificaciones generales\") se introdujo una regresi\u00f3n que bloquear\u00eda las tuber\u00edas redimensionadas bajo ciertas condiciones. Ver el reproductor en [1]. La confirmaci\u00f3n de cambio de tama\u00f1o del anillo de tuber\u00eda se movi\u00f3 a una funci\u00f3n diferente, lo que movi\u00f3 la activaci\u00f3n de pipe-&gt;wr_wait antes de aumentar pipe-&gt;max_usage. Si una tuber\u00eda estaba llena antes de que ocurriera el cambio de tama\u00f1o, la reactivaci\u00f3n nunca activar\u00eda pipe_write. Configure @max_usage y @nr_accounted antes de despertar a los escritores si no se trata de una cola de vigilancia. [Christian Brauner : reescribir en la cuenta para las colas de visualizaci\u00f3n]"}], "lastModified": "2024-11-04T13:16:45.690", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}