CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head->full_size - head->header_size" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add a check for negatives, and let's add a upper bounds check as well.

CVSS v3 8.4 HIGH

8.4^/10

CVSS v3 : HIGH

Vector :

Exploitability : 2.5 / Impact : 5.9

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://git.kernel.org/stable/c/044e220667157fb9d59320341badec59cf45ba48
https://git.kernel.org/stable/c/98f681b0f84cfc3a1d83287b77697679e0398306
https://git.kernel.org/stable/c/9eeb8e1231f6450c574c1db979122e171a1813ab
https://git.kernel.org/stable/c/ced7df8b3c5c4751244cad79011e86cf1f809153
https://git.kernel.org/stable/c/d133d67e7e724102d1e53009c4f88afaaf3e167c

Configurations

No configuration.

History

03 Jul 2024, 01:50

Type	Values Removed	Values Added
Summary		(es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: ASoC: SOF: agregue algunas comprobaciones de los límites a los datos del firmware. Smatch se queja de que "head->full_size - head->header_size" puede desbordarse. Hasta cierto punto, siempre vamos a tener que confiar un poco en el firmware. Sin embargo, es bastante fácil agregar una verificación de negativos y agreguemos también una verificación de los límites superiores.
CVSS	v2 : ~~unknown~~ v3 : ~~unknown~~	v2 : unknown v3 : 8.4
CWE		CWE-120

28 Apr 2024, 12:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2024-04-28 12:15

Updated : 2024-07-03 01:50

NVD link : CVE-2024-26927

Mitre link : CVE-2024-26927

CVE.ORG link : CVE-2024-26927

JSON object : View

Products Affected

No product.

CWE

CWE-120

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

{"id": "CVE-2024-26927", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.4, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.5}]}, "published": "2024-04-28T12:15:21.063", "references": [{"url": "https://git.kernel.org/stable/c/044e220667157fb9d59320341badec59cf45ba48", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/98f681b0f84cfc3a1d83287b77697679e0398306", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/9eeb8e1231f6450c574c1db979122e171a1813ab", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/ced7df8b3c5c4751244cad79011e86cf1f809153", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/d133d67e7e724102d1e53009c4f88afaaf3e167c", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-120"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: SOF: Add some bounds checking to firmware data\n\nSmatch complains about \"head->full_size - head->header_size\" can\nunderflow. To some extent, we're always going to have to trust the\nfirmware a bit. However, it's easy enough to add a check for negatives,\nand let's add a upper bounds check as well."}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: ASoC: SOF: agregue algunas comprobaciones de los l\u00edmites a los datos del firmware. Smatch se queja de que \"head->full_size - head->header_size\" puede desbordarse. Hasta cierto punto, siempre vamos a tener que confiar un poco en el firmware. Sin embargo, es bastante f\u00e1cil agregar una verificaci\u00f3n de negativos y agreguemos tambi\u00e9n una verificaci\u00f3n de los l\u00edmites superiores."}], "lastModified": "2024-07-03T01:50:01.863", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}