Answer in brief
CVE-2022-48816 records a High severity (CVSS 7.8) vulnerability in SUNRPC: lock against ->sock changing during sysfs read. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <fdc42287ae3f8a35cc2098307f52d7864b4bc8ed || >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <9482ab4540f5bcc869b44c067ae99b5fca16bd07 || >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <b49ea673e119f59c71645e2f65b3ccad857c90ee || 21a2be1a5145d072deedc7cdc5b2d17380abea75 || 77876473912d1bf1ed16bffa1674e5ff0f499f25 || >=5.10.67 <5.11 || >=5.13.19 <5.14 | fdc42287ae3f8a35cc2098307f52d7864b4bc8ed, 9482ab4540f5bcc869b44c067ae99b5fca16bd07, b49ea673e119f59c71645e2f65b3ccad857c90ee, 5.11, 5.14 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 16, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-48816 records a High severity (CVSS 7.8) vulnerability in SUNRPC: lock against ->sock changing during sysfs read. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.17:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <fdc42287ae3f8a35cc2098307f52d7864b4bc8ed || >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <9482ab4540f5bcc869b44c067ae99b5fca16bd07 || >=a8482488a7d6d320f63a9ee1912dbb5ae5b80a61 <b49ea673e119f59c71645e2f65b3ccad857c90ee || 21a2be1a5145d072deedc7cdc5b2d17380abea75 || 77876473912d1bf1ed16bffa1674e5ff0f499f25 || >=5.10.67 <5.11 || >=5.13.19 <5.14 | fdc42287ae3f8a35cc2098307f52d7864b4bc8ed, 9482ab4540f5bcc869b44c067ae99b5fca16bd07, b49ea673e119f59c71645e2f65b3ccad857c90ee, 5.11, 5.14 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 16, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.