NULL Pointer Dereference Affecting kernel-doc package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL8-KERNELDOC-7236998
- published 10 Jun 2024
- disclosed 21 May 2024
Introduced: 21 May 2024
CVE-2023-52749 Open this link in a new tabHow to fix?
There is no fixed version for RHEL:8
kernel-doc
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-doc
package and not the kernel-doc
package as distributed by RHEL
.
See How to fix?
for RHEL:8
relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
spi: Fix null dereference on suspend
A race condition exists where a synchronous (noqueue) transfer can be active during a system suspend. This can cause a null pointer dereference exception to occur when the system resumes.
Example order of events leading to the exception:
- spi_sync() calls __spi_transfer_message_noqueue() which sets ctlr->cur_msg
- Spi transfer begins via spi_transfer_one_message()
- System is suspended interrupting the transfer context
- System is resumed
- spi_controller_resume() calls spi_start_queue() which resets cur_msg to NULL
- Spi transfer context resumes and spi_finalize_current_message() is called which dereferences cur_msg (which is now NULL)
Wait for synchronous transfers to complete before suspending by acquiring the bus mutex and setting/checking a suspend flag.