You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE has been marked Rejected in the CVE List. These CVEs are stored in the NVD, but do not show up in search results by default.
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: kernel de Linux
Description: En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: PCI: Evite posibles lecturas fuera de los límites en pci_dev_for_each_resource() Coverity se queja de que el puntero en pci_dev_for_each_resource() puede ser incorrecto, es decir, podría usarse para lecturas fuera de los límites. No hay ningún problema real en este momento porque tenemos otra verificación posterior y no se está realizando la lectura fuera de los límites. En cualquier caso, es mejor que el código tenga esto solucionado, de ahí el cambio propuesto. Como señaló Jonas, "probablemente hace que el código tenga un rendimiento un poco menor, ya que ahora se verificará que res no sea NULL (lo que siempre será cierto), pero dudo que sea significativo (o en alguna ruta activa)".
CVE Modified by kernel.org3/03/2024 3:15:07 AM
Action
Type
Old Value
New Value
Changed
Description
In the Linux kernel, the following vulnerability has been resolved:
PCI: Avoid potential out-of-bounds read in pci_dev_for_each_resource()
Coverity complains that pointer in the pci_dev_for_each_resource() may be
wrong, i.e., might be used for the out-of-bounds read.
There is no actual issue right now because we have another check afterwards
and the out-of-bounds read is not being performed. In any case it's better
code with this fixed, hence the proposed change.
As Jonas pointed out "It probably makes the code slightly less performant
as res will now be checked for being not NULL (which will always be true),
but I doubt it will be significant (or in any hot paths)."
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Removed
Reference
Linux https://git.kernel.org/stable/c/3171e46d677a668eed3086da78671f1e4f5b8405
Removed
Reference
Linux https://git.kernel.org/stable/c/5b3e25efe16e06779a9a7c7610217c1b921ec179
Removed
Reference
Linux https://git.kernel.org/stable/c/bd26159dcaaa3e9a927070efd348e7ce7e5ee933
CVE Rejected by kernel.org3/03/2024 3:15:07 AM
Action
Type
Old Value
New Value
New CVE Received from kernel.org2/26/2024 11:27:48 AM
Action
Type
Old Value
New Value
Added
Description
In the Linux kernel, the following vulnerability has been resolved:
PCI: Avoid potential out-of-bounds read in pci_dev_for_each_resource()
Coverity complains that pointer in the pci_dev_for_each_resource() may be
wrong, i.e., might be used for the out-of-bounds read.
There is no actual issue right now because we have another check afterwards
and the out-of-bounds read is not being performed. In any case it's better
code with this fixed, hence the proposed change.
As Jonas pointed out "It probably makes the code slightly less performant
as res will now be checked for being not NULL (which will always be true),
but I doubt it will be significant (or in any hot paths)."
Added
Reference
Linux https://git.kernel.org/stable/c/3171e46d677a668eed3086da78671f1e4f5b8405 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/5b3e25efe16e06779a9a7c7610217c1b921ec179 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/bd26159dcaaa3e9a927070efd348e7ce7e5ee933 [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2023-52466 NVD
Published Date: 02/26/2024 NVD
Last Modified: 03/03/2024
Source: kernel.org