CVE-2022-48816
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.3%
21.3th percentile
CISA KEV
Not listed
Weakness / dates
CWE-476
Published 2024-07-16 · modified 2026-08-04
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2024-07-16 — Published (NVD)
- 2026-08-04 — Last modified (NVD)
Description
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.
Affected
References
- https://git.kernel.org/stable/c/9482ab4540f5bcc869b44c067ae99b5fca16bd07
- https://git.kernel.org/stable/c/b49ea673e119f59c71645e2f65b3ccad857c90ee
- https://git.kernel.org/stable/c/fdc42287ae3f8a35cc2098307f52d7864b4bc8ed
- https://git.kernel.org/stable/c/9482ab4540f5bcc869b44c067ae99b5fca16bd07
- https://git.kernel.org/stable/c/b49ea673e119f59c71645e2f65b3ccad857c90ee