References to Advisories, Solutions, and Tools

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 nvd@nist.gov.

Change History

kernel.org https://git.kernel.org/stable/c/aa3f3d7bef59583f2d3234173105a27ff61ef8fe [No types assigned]

kernel.org https://git.kernel.org/stable/c/c8dce228db6f81dbc897a018dfc5c418e917cf64 [No types assigned]

In the Linux kernel, the following vulnerability has been resolved:

spi: Fix deadlock when adding SPI controllers on SPI buses

Currently we have a global spi_add_lock which we take when adding new
devices so that we can check that we're not trying to reuse a chip
select that's already controlled.  This means that if the SPI device is
itself a SPI controller and triggers the instantiation of further SPI
devices we trigger a deadlock as we try to register and instantiate
those devices while in t

kernel.org https://git.kernel.org/stable/c/6098475d4cb48d821bdf453c61118c56e26294f0 [No types assigned]

kernel.org https://git.kernel.org/stable/c/722ef19a161ce3fffb3d1b01ce2301c306639bdd [No types assigned]