BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49321High confidence

xprtrdma: treat all calls not a bcall when bc_serv is NULL

Linux · Linux

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 4 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-54906

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a bcall when bc service is not exist. The debug message at rpcrdma_bc_receive_call are, [56579.837169] RPC: rpcrdma_bc_receive_call: callback XID 00000001, length=20 [56579.837174] RPC: rpcrdma_bc_receive_call: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 After that, rpcrdma_bc_receive_call will meets NULL pointer as, [ 226.057890] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c8 ... [ 226.058704] RIP: 0010:_raw_spin_lock+0xc/0x20 ... [ 226.059732] Call Trace: [ 226.059878] rpcrdma_bc_receive_call+0x138/0x327 [rpcrdma] [ 226.060011] __ib_process_cq+0x89/0x170 [ib_core] [ 226.060092] ib_cq_poll_work+0x26/0x80 [ib_core] [ 226.060257] process_one_work+0x1a7/0x360 [ 226.060367] ? create_worker+0x1a0/0x1a0 [ 226.060440] worker_thread+0x30/0x390 [ 226.060500] ? create_worker+0x1a0/0x1a0 [ 226.060574] kthread+0x116/0x130 [ 226.060661] ? kthread_flush_work_fn+0x10/0x10 [ 226.060724] ret_from_fork+0x35/0x40 ...

What

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a bcall when bc service is not exist. The debug message at rpcrdma_bc_receive_call are, [56579.837169] RPC: rpcrdma_bc_receive_call: callback XID 00000001, length=20 [56579.837174] RPC: rpcrdma_bc_receive_call: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 After that, rpcrdma_bc_receive_call will meets NULL pointer as, [ 226.057890] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c8 ... [ 226.058704] RIP: 0010:_raw_spin_lock+0xc/0x20 ... [ 226.059732] Call Trace: [ 226.059878] rpcrdma_bc_receive_call+0x138/0x327 [rpcrdma] [ 226.060011] __ib_process_cq+0x89/0x170 [ib_core] [ 226.060092] ib_cq_poll_work+0x26/0x80 [ib_core] [ 226.060257] process_one_work+0x1a7/0x360 [ 226.060367] ? create_worker+0x1a0/0x1a0 [ 226.060440] worker_thread+0x30/0x390 [ 226.060500] ? create_worker+0x1a0/0x1a0 [ 226.060574] kthread+0x116/0x130 [ 226.060661] ? kthread_flush_work_fn+0x10/0x10 [ 226.060724] ret_from_fork+0x35/0x40 ...

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a bcall when bc service is not exist. The debug message at rpcrdma_bc_receive_call are, [56579.837169] RPC: rpcrdma_bc_receive_call: callback XID 00000001, length=20 [56579.837174] RPC: rpcrdma_bc_receive_call: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 After that, rpcrdma_bc_receive_call will meets NULL pointer as, [ 226.057890] BUG: unable to handle kernel NULL pointer dereference at 00000000000000c8 ... [ 226.058704] RIP: 0010:_raw_spin_lock+0xc/0x20 ... [ 226.059732] Call Trace: [ 226.059878] rpcrdma_bc_receive_call+0x138/0x327 [rpcrdma] [ 226.060011] __ib_process_cq+0x89/0x170 [ib_core] [ 226.060092] ib_cq_poll_work+0x26/0x80 [ib_core] [ 226.060257] process_one_work+0x1a7/0x360 [ 226.060367] ? create_worker+0x1a0/0x1a0 [ 226.060440] worker_thread+0x30/0x390 [ 226.060500] ? create_worker+0x1a0/0x1a0 [ 226.060574] kthread+0x116/0x130 [ 226.060661] ? kthread_flush_work_fn+0x10/0x10 [ 226.060724] ret_from_fork+0x35/0x40 ...

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49269 Référence CVE CVE-2022-49272 https://www.cve.org/CVERecord?id=CVE-2022-49272 Référence CVE CVE-2022-49273 https://www.cve.org/CVERecord?id=CVE-2022-49273 Référence CVE CVE-2022-49279 https://www.cve.org/CVERecord?id=CVE-2022-49279 Référence CVE CVE-2022-49286 https://www.cve.org/CVERecord?id=CVE-2022-49286 Référence CVE CVE-2022-49290 https://www.cve.org/CVERecord?id=CVE-2022-49290 Référence CVE CVE-2022-49297 https://www.cve.org/CVERecord?id=CVE-2022-49297 Référence CVE CVE-2022-49307 https://www.cve.org/CVERecord?id=CVE-2022-49307 Référence CVE CVE-2022-49308 https://www.cve.org/CVERecord?id=CVE-2022-49308 Référence CVE CVE-2022-49321 https://www.cve.org/CVERecord?id=CVE-2022-49321 Référence CVE CVE-2022-49322 https://www.cve.org/CVERecord?id=CVE-2022-49322 Référence CVE CVE-2022-49323 https://www.cve.org/CVERecord?id=CVE-2022-49323 Référence CVE CVE-2022-49330 https://www.cve.org/CVERecord?id=CVE-2022-49330 Référence CVE CVE-2022-49334 https://www.cve.org/CVERecord?id=CVE-2022-49334 Référence CVE CVE-2022-49339 https://www.cve.org/CVERecord?id=CVE-2022-49339 Référence CVE CVE-2022-49340 https://www.cve.org/CVERecord?id=CVE-2022-49340 Référence CVE CVE-2022-49341 https://www.cve.org/CVERecord?id=CVE-2022-49341 Référence CVE CVE-2022-49343 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0336Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49310 Référence CVE CVE-2022-49311 https://www.cve.org/CVERecord?id=CVE-2022-49311 Référence CVE CVE-2022-49312 https://www.cve.org/CVERecord?id=CVE-2022-49312 Référence CVE CVE-2022-49313 https://www.cve.org/CVERecord?id=CVE-2022-49313 Référence CVE CVE-2022-49314 https://www.cve.org/CVERecord?id=CVE-2022-49314 Référence CVE CVE-2022-49315 https://www.cve.org/CVERecord?id=CVE-2022-49315 Référence CVE CVE-2022-49316 https://www.cve.org/CVERecord?id=CVE-2022-49316 Référence CVE CVE-2022-49319 https://www.cve.org/CVERecord?id=CVE-2022-49319 Référence CVE CVE-2022-49320 https://www.cve.org/CVERecord?id=CVE-2022-49320 Référence CVE CVE-2022-49321 https://www.cve.org/CVERecord?id=CVE-2022-49321 Référence CVE CVE-2022-49322 https://www.cve.org/CVERecord?id=CVE-2022-49322 Référence CVE CVE-2022-49323 https://www.cve.org/CVERecord?id=CVE-2022-49323 Référence CVE CVE-2022-49325 https://www.cve.org/CVERecord?id=CVE-2022-49325 Référence CVE CVE-2022-49326 https://www.cve.org/CVERecord?id=CVE-2022-49326 Référence CVE CVE-2022-49327 https://www.cve.org/CVERecord?id=CVE-2022-49327 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49329 https://www.cve.org/CVERecord?id=CVE-2022-49329 Référence CVE CVE-2022-49330 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0307Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49310 Référence CVE CVE-2022-49311 https://www.cve.org/CVERecord?id=CVE-2022-49311 Référence CVE CVE-2022-49312 https://www.cve.org/CVERecord?id=CVE-2022-49312 Référence CVE CVE-2022-49313 https://www.cve.org/CVERecord?id=CVE-2022-49313 Référence CVE CVE-2022-49314 https://www.cve.org/CVERecord?id=CVE-2022-49314 Référence CVE CVE-2022-49315 https://www.cve.org/CVERecord?id=CVE-2022-49315 Référence CVE CVE-2022-49316 https://www.cve.org/CVERecord?id=CVE-2022-49316 Référence CVE CVE-2022-49319 https://www.cve.org/CVERecord?id=CVE-2022-49319 Référence CVE CVE-2022-49320 https://www.cve.org/CVERecord?id=CVE-2022-49320 Référence CVE CVE-2022-49321 https://www.cve.org/CVERecord?id=CVE-2022-49321 Référence CVE CVE-2022-49322 https://www.cve.org/CVERecord?id=CVE-2022-49322 Référence CVE CVE-2022-49323 https://www.cve.org/CVERecord?id=CVE-2022-49323 Référence CVE CVE-2022-49325 https://www.cve.org/CVERecord?id=CVE-2022-49325 Référence CVE CVE-2022-49326 https://www.cve.org/CVERecord?id=CVE-2022-49326 Référence CVE CVE-2022-49327 https://www.cve.org/CVERecord?id=CVE-2022-49327 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49329 https://www.cve.org/CVERecord?id=CVE-2022-49329 Référence CVE CVE-2022-49330 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0252Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49310 Référence CVE CVE-2022-49311 https://www.cve.org/CVERecord?id=CVE-2022-49311 Référence CVE CVE-2022-49312 https://www.cve.org/CVERecord?id=CVE-2022-49312 Référence CVE CVE-2022-49313 https://www.cve.org/CVERecord?id=CVE-2022-49313 Référence CVE CVE-2022-49314 https://www.cve.org/CVERecord?id=CVE-2022-49314 Référence CVE CVE-2022-49315 https://www.cve.org/CVERecord?id=CVE-2022-49315 Référence CVE CVE-2022-49316 https://www.cve.org/CVERecord?id=CVE-2022-49316 Référence CVE CVE-2022-49319 https://www.cve.org/CVERecord?id=CVE-2022-49319 Référence CVE CVE-2022-49320 https://www.cve.org/CVERecord?id=CVE-2022-49320 Référence CVE CVE-2022-49321 https://www.cve.org/CVERecord?id=CVE-2022-49321 Référence CVE CVE-2022-49322 https://www.cve.org/CVERecord?id=CVE-2022-49322 Référence CVE CVE-2022-49323 https://www.cve.org/CVERecord?id=CVE-2022-49323 Référence CVE CVE-2022-49326 https://www.cve.org/CVERecord?id=CVE-2022-49326 Référence CVE CVE-2022-49327 https://www.cve.org/CVERecord?id=CVE-2022-49327 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49331 https://www.cve.org/CVERecord?id=CVE-2022-49331 Référence CVE CVE-2022-49332 https://www.cve.org/CVERecord?id=CVE-2022-49332 Référence CVE CVE-2022-49335 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
63cae47005af51c937f4cdcc4835f29075add2ba < 8e3943c50764dc7c5f25911970c3ff062ec1f18c; 63cae47005af51c937f4cdcc4835f29075add2ba < 998d35a2aff4b81a1c784f3aa45cd3afff6814c1; 63cae47005af51c937f4cdcc4835f29075add2ba < da99331fa62131a38a0947a8204c5208de7b0454; 63cae47005af51c937f4cdcc4835f29075add2ba < 8dbae5affbdbf524b48000f9d357925bb001e5f4; 63cae47005af51c937f4cdcc4835f29075add2ba < a3fc8051ee061e31db13e2fe011e8e0b71a7f815; 63cae47005af51c937f4cdcc4835f29075add2ba < 90c4f73104016748533a5707ecd15930fbeff402; 63cae47005af51c937f4cdcc4835f29075add2ba < 91784f3d77b73885e1b2e6b59d3cbf0de0a1126a; 63cae47005af51c937f4cdcc4835f29075add2ba < 11270e7ca268e8d61b5d9e5c3a54bd1550642c9c
Fixed
< 4.4; 4.14.283 ≤ 4.14.*; 4.19.247 ≤ 4.19.*; 5.4.198 ≤ 5.4.*; 5.10.122 ≤ 5.10.*; 5.15.47 ≤ 5.15.*; 5.17.15 ≤ 5.17.*; 5.18.4 ≤ 5.18.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 5 Aug 2026, 08:54 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-54906
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-54906↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49321 · cve.blacktree.nl