SUNRPC: Fix the svc_deferred_event trace class
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be relied upon in the tracepoint to provide the remote's address. Unfortunately we can't revert the "svc_deferred_class" hunk in commit ece200ddd54b ("sunrpc: Save remote presentation address in svc_xprt for trace events") because there is now a specific check of event format specifiers for unsafe dereferences. The warning that check emits is: event svc_defer_recv has unsafe dereference of argument 1 A "%pISpc" format specifier with a "struct sockaddr *" is indeed flagged by this check. Instead, take the brute-force approach used by the svcrdma_qp_error tracepoint. Convert the dr::addr field into a presentation address in the TP_fast_assign() arm of the trace event, and store that as a string. This fix can be backported to -stable kernels. In the meantime, commit c6ced22997ad ("tracing: Update print fmt check to handle new __get_sockaddr() macro") is now in v5.18, so this wonky fix can be replaced with __sockaddr() and friends properly during the v5.19 merge window.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.112, 5.15.35, 5.17.4
- CVEs
- CVE-2022-49065
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 21:36 UTC · Revision 1
Source evidence
SUNRPC: Fix the svc_deferred_event trace class
core-osv · Original sourcePublished 26 Feb 2025, 01:54 UTC
In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be relied upon in the tracepoint to provide the remote's address. Unfortunately we can't revert the "svc_deferred_class" hunk in commit ece200ddd54b ("sunrpc: Save remote presentation address in svc_xprt for trace events") because there is now a specific check of event format specifiers for unsafe dereferences. The warning that check emits is: event svc_defer_recv has unsafe dereference of argument 1 A "%pISpc" format specifier with a "struct sockaddr *" is indeed flagged by this check. Instead, take the brute-force approach used by the svcrdma_qp_error tracepoint. Convert the dr::addr field into a presentation address in the TP_fast_assign() arm of the trace event, and store that as a string. This fix can be backported to -stable kernels. In the meantime, commit c6ced22997ad ("tracing: Update print fmt check to handle new __get_sockaddr() macro") is now in v5.18, so this wonky fix can be replaced with __sockaddr() and friends properly during the v5.19 merge window.
osv:CVE-2022-49065
Kernel
Fixed versions: 5.10.112, 5.15.35, 5.17.4
Complete source record
{
"id": "7f9b4943e61ba10c9dc304fcfd78e4f29a8ee85e4df99e65d11787aa1b3ef119",
"url": "https://osv.dev/vulnerability/CVE-2022-49065",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "SUNRPC: Fix the svc_deferred_event trace class",
"summary": "In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be relied upon in the tracepoint to provide the remote's address. Unfortunately we can't revert the \"svc_deferred_class\" hunk in commit ece200ddd54b (\"sunrpc: Save remote presentation address in svc_xprt for trace events\") because there is now a specific check of event format specifiers for unsafe dereferences. The warning that check emits is: event svc_defer_recv has unsafe dereference of argument 1 A \"%pISpc\" format specifier with a \"struct sockaddr *\" is indeed flagged by this check. Instead, take the brute-force approach used by the svcrdma_qp_error tracepoint. Convert the dr::addr field into a presentation address in the TP_fast_assign() arm of the trace event, and store that as a string. This fix can be backported to -stable kernels. In the meantime, commit c6ced22997ad (\"tracing: Update print fmt check to handle new __get_sockaddr() macro\") is now in v5.18, so this wonky fix can be replaced with __sockaddr() and friends properly during the v5.19 merge window.",
"evidence": "osv:CVE-2022-49065",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.112",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.35",
"evidence": "/affected/1/ranges"
},
{
"value": "5.17.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2022-49065",
"aliases": [
"CVE-2022-49065"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "ece200ddd54b9ce840cfee554fb812560c545c7d"
},
{
"fixed": "85ee17ca21cf92989e8c923e3ea4514c291e9d38"
},
{
"fixed": "726ae7300fcc25fefa46d188cc07eb16dc908f9e"
},
{
"fixed": "c2456f470eea3bd06574d988bf6089e7c3f4c5cc"
},
{
"fixed": "4d5004451ab2218eab94a30e1841462c9316ba19"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49065.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.17.0"
},
{
"fixed": "5.10.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.35"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.17.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49065.json"
}
}
],
"modified": "2026-10-28T02:30:23.930860641Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4d5004451ab2218eab94a30e1841462c9316ba19",
"https://git.kernel.org/stable/c/726ae7300fcc25fefa46d188cc07eb16dc908f9e",
"https://git.kernel.org/stable/c/85ee17ca21cf92989e8c923e3ea4514c291e9d38",
"https://git.kernel.org/stable/c/c2456f470eea3bd06574d988bf6089e7c3f4c5cc",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49065.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49065",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49065.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49065",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 490323,
"published_at": "2025-02-26T01:54:33.881+00:00"
}