NFSD: stop registering with rpcbind after a failure in listener_set
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f21188d163fe7a6c930ef387af5937b9f7322725, Kernel 76ca00a4eca507550af13118289169bc4b508b82, Kernel bf0f3a37e6ccb78ae80cc6eb2edde4f033c7574c and 4 more.
In the Linux kernel, the following vulnerability has been resolved: NFSD: stop registering with rpcbind after a failure in listener_set nfsd_nl_listener_set_doit() calls svc_xprt_create_from_sa() once for each requested listener and passes flags of 0, so every listener registers with rpcbind on its own. A rpcbind that accepts the connection and never replies therefore costs one timeout for each entry. With the cap of 1024 entries the request can hold nfsd_mutex for about 34 minutes, which is roughly 17 times the hung-task threshold. One failure is enough to know that the next call will not fare better. Read svc_rpcb_failure_count() before the create loop, and pass SVC_SOCK_ANONYMOUS for the rest of the request once the count moves.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=16a471177496c8e04a9793812c187a2c1a2192fa <f21188d163fe7a6c930ef387af5937b9f7322725, >=16a471177496c8e04a9793812c187a2c1a2192fa <76ca00a4eca507550af13118289169bc4b508b82, >=16a471177496c8e04a9793812c187a2c1a2192fa <bf0f3a37e6ccb78ae80cc6eb2edde4f033c7574c, >=16a471177496c8e04a9793812c187a2c1a2192fa <d7515faec4d1b3c67c1c18ec28abad83d90ef8c1, =6.10 | f21188d163fe7a6c930ef387af5937b9f7322725, 76ca00a4eca507550af13118289169bc4b508b82, bf0f3a37e6ccb78ae80cc6eb2edde4f033c7574c, d7515faec4d1b3c67c1c18ec28abad83d90ef8c1 |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=6.10.0 <6.12.118 | 6.18.64, 7.3.5, 6.12.118 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket