Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2025-68379 — kernel

🟠 CVSS 7.8 — High ✅ No Known Exploit NVD
7.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

RDMA/rxe: Fix null deref on srq->rq.queue after resize failure

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Fix null deref on srq->rq.queue after resize failure

A NULL pointer dereference can occur in rxe_srq_chk_attr() when

ibv_modify_srq() is invoked twice in succession under certain error

conditions. The first call may fail in rxe_queue_resize(), which leads

rxe_srq_from_attr() to set srq->rq.queue = NULL. The second call then

triggers a crash (null deref) when accessing

srq->rq.queue->buf->index_mask.

Call Trace:

<TASK>

rxe_modify_srq+0x170/0x480 [rdma_rxe]

? __pfx_rxe_modify_srq+0x10/0x10 [rdma_rxe]

? uverbs_try_lock_object+0x4f/0xa0 [ib_uverbs]

? rdma_lookup_get_uobject+0x1f0/0x380 [ib_uverbs]

ib_uverbs_modify_srq+0x204/0x290 [ib_uverbs]

? __pfx_ib_uverbs_modify_srq+0x10/0x10 [ib_uverbs]

? tryinc_node_nr_active+0xe6/0x150

? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]

ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x2c0/0x470 [ib_uverbs]

? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]

? uverbs_fill_udata+0xed/0x4f0 [ib_uverbs]

ib_uverbs_run_method+0x55a/0x6e0 [ib_uverbs]

? __pfx_ib_uverbs_handler_UVERBS_METHOD_INVOKE_WRITE+0x10/0x10 [ib_uverbs]

ib_uverbs_cmd_verbs+0x54d/0x800 [ib_uverbs]

? __pfx_ib_uverbs_cmd_verbs+0x10/0x10 [ib_uverbs]

? __pfx___raw_spin_lock_irqsave+0x10/0x10

? __pfx_do_vfs_ioctl+0x10/0x10

? ioctl_has_perm.constprop.0.isra.0+0x2c7/0x4c0

? __pfx_ioctl_has_perm.constprop.0.isra.0+0x10/0x10

ib_uverbs_ioctl+0x13e/0x220 [ib_uverbs]

? __pfx_ib_uverbs_ioctl+0x10/0x10 [ib_uverbs]

__x64_sys_ioctl+0x138/0x1c0

do_syscall_64+0x82/0x250

? fdget_pos+0x58/0x4c0

? ksys_write+0xf3/0x1c0

? __pfx_ksys_write+0x10/0x10

? do_syscall_64+0xc8/0x250

? __pfx_vm_mmap_pgoff+0x10/0x10

? fget+0x173/0x230

? fput+0x2a/0x80

? ksys_mmap_pgoff+0x224/0x4c0

? do_syscall_64+0xc8/0x250

? do_user_addr_fault+0x37b/0xfe0

? clear_bhb_loop+0x50/0xa0

? clear_bhb_loop+0x50/0xa0

? clear_bhb_loop+0x50/0xa0

entry_SYSCALL_64_after_hwframe+0x76/0x7e

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

Affected software

CVE-2025-68379 is recorded against 2 packages.

  • kernel (from 6.18.0 up to 6.18.2)
  • unknown

Timeline and source

Published on 24 December 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2025-68379 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity High
CVSS Score 7.8
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-12-24
Updated 2026-08-20
Modified 2026-08-12
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel 6.18.0 6.18.2
unknown

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2025-68379 is rated CVSS 7.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.