SUNRPC: lock against ->sock changing during sysfs read
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.14, 5.15.209, 5.16.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: lock against ->sock changing during sysfs read ->sock can be set to NULL asynchronously unless ->recv_mutex is held. So it is important to hold that mutex. Otherwise a sysfs read can trigger an oops. Commit 17f09d3f619a ("SUNRPC: Check if the xprt is connected before handling sysfs reads") appears to attempt to fix this problem, but it only narrows the race window.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 21a2be1a5145d072deedc7cdc5b2d17380abea75 · fixed in cd366b9091a3e6ed8229e4b908e895d20b527dc0; From a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 · fixed in fdc42287ae3f8a35cc2098307f52d7864b4bc8ed; From a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 · fixed in 9482ab4540f5bcc869b44c067ae99b5fca16bd07; From a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 · fixed in b49ea673e119f59c71645e2f65b3ccad857c90ee; From 5.10.67 · fixed in 5.10.271; From 5.13.19 · fixed in 5.14
- Linux Linux
5.14
- KernelLinux
fixed in 5.10.271; From 5.11.0 · fixed in 5.15.209; From 5.14.0 · fixed in 5.16.10