mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-07-09 16:05:11 +00:00
33 lines
3.4 KiB
JSON
33 lines
3.4 KiB
JSON
{
|
|
"id": "CVE-2024-58006",
|
|
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
|
"published": "2025-02-27T03:15:11.583",
|
|
"lastModified": "2025-02-27T03:15:11.583",
|
|
"vulnStatus": "Awaiting Analysis",
|
|
"cveTags": [],
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar()\n\nIn commit 4284c88fff0e (\"PCI: designware-ep: Allow pci_epc_set_bar() update\ninbound map address\") set_bar() was modified to support dynamically\nchanging the backing physical address of a BAR that was already configured.\n\nThis means that set_bar() can be called twice, without ever calling\nclear_bar() (as calling clear_bar() would clear the BAR's PCI address\nassigned by the host).\n\nThis can only be done if the new BAR size/flags does not differ from the\nexisting BAR configuration. Add these missing checks.\n\nIf we allow set_bar() to set e.g. a new BAR size that differs from the\nexisting BAR size, the new address translation range will be smaller than\nthe BAR size already determined by the host, which would mean that a read\npast the new BAR size would pass the iATU untranslated, which could allow\nthe host to read memory not belonging to the new struct pci_epf_bar.\n\nWhile at it, add comments which clarifies the support for dynamically\nchanging the physical address of a BAR. (Which was also missing.)"
|
|
},
|
|
{
|
|
"lang": "es",
|
|
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: PCI: dwc: ep: Impedir cambiar el tama\u00f1o/indicadores de BAR en pci_epc_set_bar() En el commit 4284c88fff0e (\"PCI: designware-ep: Permitir que pci_epc_set_bar() actualice la direcci\u00f3n del mapa de entrada\"), se modific\u00f3 set_bar() para admitir el cambio din\u00e1mico de la direcci\u00f3n f\u00edsica de respaldo de un BAR que ya estaba configurado. Esto significa que se puede llamar a set_bar() dos veces, sin llamar nunca a clear_bar() (ya que llamar a clear_bar() borrar\u00eda la direcci\u00f3n PCI del BAR asignada por el host). Esto solo se puede hacer si el nuevo tama\u00f1o/indicadores de BAR no difieren de la configuraci\u00f3n de BAR existente. Agregue estas comprobaciones faltantes. Si permitimos que set_bar() establezca, por ejemplo, un nuevo tama\u00f1o de BAR que difiere del tama\u00f1o de BAR existente, el nuevo rango de traducci\u00f3n de direcciones ser\u00e1 m\u00e1s peque\u00f1o que el tama\u00f1o de BAR ya determinado por el host, lo que significar\u00eda que una lectura m\u00e1s all\u00e1 del nuevo tama\u00f1o de BAR pasar\u00eda la iATU sin traducir, lo que podr\u00eda permitir que el host lea memoria que no pertenece a la nueva estructura pci_epf_bar. Mientras tanto, agregue comentarios que aclaren el soporte para cambiar din\u00e1micamente la direcci\u00f3n f\u00edsica de un BAR. (Lo cual tambi\u00e9n faltaba)."
|
|
}
|
|
],
|
|
"metrics": {},
|
|
"references": [
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/3229c15d6267de8e704b4085df8a82a5af2d63eb",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/3708acbd5f169ebafe1faa519cb28adc56295546",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
},
|
|
{
|
|
"url": "https://git.kernel.org/stable/c/b5cacfd067060c75088363ed3e19779078be2755",
|
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
|
}
|
|
]
|
|
} |