CVE-2024-56688: sunrpc: clear XPRT_SOCK_UPD_TIMEOUT when reset transport
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: clear XPRTSOCKUPDTIMEOUT when reset transport
Since transport->sock has been set to NULL during reset transport, XPRTSOCKUPDTIMEOUT also needs to be cleared. Otherwise, the xstcpsetsockettimeouts() may be triggered in xstcpsendrequest() to dereference the transport->sock that has been set to NULL.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: clear XPRTSOCKUPDTIMEOUT when reset transport
Since transport->sock has been set to NULL during reset transport, XPRTSOCKUPDTIMEOUT also needs to be cleared. Otherwise, the xstcpsetsockettimeouts() may be triggered in xstcpsendrequest() to dereference the transport->sock that has been set to NULL.
— NVD
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-56688?
CVE-2024-56688 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-56688?
To fix CVE-2024-56688, update your Linux kernel to a version that has addressed this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-56688?
CVE-2024-56688 affects Linux kernel versions from 4.11 up to 6.12.2, excluding patched versions.
What component is primarily impacted by CVE-2024-56688?
CVE-2024-56688 primarily impacts the sunrpc component of the Linux kernel.
Is there a workaround for CVE-2024-56688 if I cannot update immediately?
Currently, there is no documented workaround for CVE-2024-56688, and updating is the recommended action.