CVE-2022-48925: RDMA/cma: Do not change route.addr.src_addr outside state checks
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 00265efbd3e5705038c9492a434fda8cf960c8a2, 22e9f71072fa605cbf033158db58e0790101928d, 5b1cef5798b4fd6e4fd5522e7b8a26248beeacaa.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00265efbd3e5705038c9492a434fda8cf960c8a2, 22e9f71072fa605cbf033158db58e0790101928d, 5b1cef5798b4fd6e4fd5522e7b8a26248beeacaa or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Do not change route.addr.src_addr outside state checks If the state is not idle then resolve_prepare_src() should immediately fail and no change to global state should happen. However, it unconditionally overwrites the src_addr trying to build a temporary any address. For instance if the state is already RDMA_CM_LISTEN then this will corrupt the src_addr and would cause the test in cma_cancel_operation(): if (cma_any_addr(cma_src_addr(id_priv)) && !id_priv->cma_dev) Which would manifest as this trace from syzkaller: BUG: KASAN: use-after-free in __list_add_valid+0x93/0xa0 lib/list_debug.c:26 Read of size 8 at addr ffff8881546491e0 by task syz-executor.1/32204 CPU: 1 PID: 32204 Comm: syz-executor.1 Not tainted 5.12.0-rc8-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x141/0x1d7 lib/dump_stack.c:120 print_address_description.constprop.0.cold+0x5b/0x2f8 mm/kasan/report.c:232 __kasan_report mm/kasan/report.c:399 [inline] kasan_report.cold+0x7c/0xd8 mm/kasan/report.c:416 __list_add_valid+0x93/0xa0 lib/list_debug.c:26 __list_add include/linux/list.h:67 [inline] list_add_tail include/linux/list.h:100 [inline] cma_listen_on_all drivers/infiniband/core/cma.c:2557 [inline] rdma_listen+0x787/0xe00 drivers/infiniband/core/cma.c:3751 ucma_listen+0x16a/0x210 drivers/infiniband/core/ucma.c:1102 ucma_write+0x259/0x350 drivers/infiniband/core/ucma.c:1732 vfs_write+0x28e/0xa30 fs/read_write.c:603 ksys_write+0x1ee/0x250 fs/read_write.c:658 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x44/0xae This is indicating that an rdma_id_private was destroyed without doing cma_cancel_listens(). Instead of trying to re-use the src_addr memory to indirectly create an any address derived from the dst build one explicitly on the stack and bind to that as any other normal flow would do. rdma_bind_addr() will copy it over the src_addr once it knows the state is valid. This is similar to commit bc0bdc5afaa7 ("RDMA/cma: Do not change route.addr.src_addr.ss_family")
- Published
- Aug 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.10.103
- linux linux kernel5.11 and later · before 5.15.26
- linux linux kernel5.16 and later · before 5.16.12
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 732d41c545bb359cbb8c94698bdc1f8bcf82279c and later · before 5b1cef5798b4fd6e4fd5522e7b8a26248beeacaaaffected · git
- 732d41c545bb359cbb8c94698bdc1f8bcf82279c and later · before 00265efbd3e5705038c9492a434fda8cf960c8a2affected · git
- 732d41c545bb359cbb8c94698bdc1f8bcf82279c and later · before d350724795c7a48b05bf921d94699fbfecf7da0baffected · git
- 732d41c545bb359cbb8c94698bdc1f8bcf82279c and later · before 22e9f71072fa605cbf033158db58e0790101928daffected · git
- before 5.10not affected · semver
- 5.10.103 and later · up to and including 5.10.*not affected · semver
- 5.15.26 and later · up to and including 5.15.*not affected · semver
- 5.16.12 and later · up to and including 5.16.*not affected · semver
- 5.17 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.16.12-1 | 5.16.12-1 |
| SUSE:Linux Enterprise High Availability Extension 12 SP5 | kernel-default | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-default-base | before 5.3.18-150200.24.203.1.150200.9.105.1 | 5.3.18-150200.24.203.1.150200.9.105.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-docs | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-obs-build | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-preempt | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-source | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | kernel-syms | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_60 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-default | before 5.3.18-150200.24.203.1 | 5.3.18-150200.24.203.1 |
| SUSE:Linux Enterprise Live Patching 15 SP2 | kernel-livepatch-SLE15-SP2_Update_52 | before 1-150200.5.3.1 | 1-150200.5.3.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt_debug | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-source-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-syms-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-docs | before 4.12.14-122.228.2 | 4.12.14-122.228.2 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-obs-build | before 4.12.14-122.228.2 | 4.12.14-122.228.2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48923Aug 21, 2024 · btrfs: prevent copying too big compressed lzo segment22Monitor
- ← EarlierCVE-2022-48924Aug 21, 2024 · thermal: int340x: fix memory leak in int3400_notify()22Monitor
- Later →CVE-2022-48926Aug 22, 2024 · usb: gadget: rndis: add spinlock for rndis response list31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 00265efbd3e5705038c9492a434fda8cf960c8a2 | Vendor (CNA) |
| Linux Linux | 22e9f71072fa605cbf033158db58e0790101928d | Vendor (CNA) |
| Linux Linux | 5b1cef5798b4fd6e4fd5522e7b8a26248beeacaa | Vendor (CNA) |
| Linux Linux | d350724795c7a48b05bf921d94699fbfecf7da0b | Vendor (CNA) |
| debian:linux | 5.16.12-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-azure | 4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.228.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5 | Package registry (OSV) |
| suse:kernel-docs | 4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-rt_debug | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_60 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1311 · Aug 22, 2024(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.