LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48816: SUNRPC: lock against ->sock changing during sysfs read

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can let a read of a SUNRPC sysfs entry hit a timing bug and trigger a kernel oops. The practical business risk is availability disruption on affected Linux systems, especially where SUNRPC/NFS is used. The provided sources do not show active exploitation or a scored severity.

Executive priority

Handle through normal kernel patch governance, with higher priority for production file-service and NFS-dependent systems. Do not classify as emergency based only on this bundle because severity, CVSS, and exploitation evidence are missing.

Technical view

SUNRPC sysfs read handling accessed xprt->sock while it could be set to NULL asynchronously. The fix is to hold recv_mutex during the read path. A previous connected-state check only narrowed the race window. Impact described by the source is a kernel oops, with no exploitability details provided.

Likely exposure

Exposure is limited to Linux kernels identified as affected in the CVE data and systems reaching the relevant SUNRPC sysfs read path. Exact exposure depends on distro backports and kernel packaging. The source does not define remote reachability or required privileges.

Exploitation context

The record says a sysfs read can trigger an oops. CISA KEV status is false in the bundle, and no cited source states active exploitation. Treat this as a reliability and availability concern until vendor guidance says otherwise.

Researcher notes

The key condition is a race on xprt->sock during SUNRPC sysfs reads when recv_mutex is not held. The source only states oops impact, so avoid assuming privilege escalation, remote exploitation, or broader products beyond Linux kernel builds.

Mitigation direction

  • Apply vendor kernel updates that include the referenced SUNRPC fixes.
  • Prioritize systems using NFS, SUNRPC, or related kernel RPC services.
  • Check distribution advisories for backported fixes and corrected package versions.
  • If no vendor fix is available, follow vendor guidance for temporary risk reduction.

Validation and detection

  • Inventory Linux kernel versions and distribution package revisions across assets.
  • Confirm whether vendor packages include the referenced stable kernel commits.
  • Review systems using NFS or SUNRPC for higher operational priority.
  • Track for kernel oops reports mentioning SUNRPC or xprt sysfs reads.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48816 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa8482488a7d6d320f63a9ee1912dbb5ae5b80a61, a8482488a7d6d320f63a9ee1912dbb5ae5b80a61, a8482488a7d6d320f63a9ee1912dbb5ae5b80a61, 21a2be1a5145d072deedc7cdc5b2d17380abea75, 77876473912d1bf1ed16bffa1674e5ff0f499f25, 5.10.67, 5.13.19unaffected
LinuxLinux5.14, 0, 5.15.209, 5.16.10, 5.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.