CVE-2026-89549

sunrpc: route to a populated pool in svc_pool_for_cpu()

HIGH
7.5
CVSS Score
Published: September 11, 2026 at 07:44 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: sunrpc: route to a populated pool in svc_pool_for_cpu() svc_set_num_threads() spreads the requested threads evenly across the service's pools (base = nrservs / sv_nrpools). When a service runs fewer threads than it has pools -- e.g. an nfsd configured with fewer threads than the host has NUMA nodes while running in "pernode" or "percpu" mode -- the trailing pools are left with no threads at all. svc_xprt_enqueue() selects a pool from the CPU servicing the transport, queues the transport on that pool's sp_xprts, and only wakes a thread from the same pool. Each thread services exclusively its own pool, so a transport that lands on a threadless pool is enqueued on sp_xprts and never picked up: the connection hangs indefinitely. Have svc_pool_for_cpu() skip pools that currently have no threads, falling back to the next populated pool. This trades NUMA locality for a guarantee that the work is actually serviced. sp_nrthreads is only updated under the service mutex; the lockless read here is a best-effort routing hint, so annotate it with data_race().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.19bfd241600a3b0db4fe43c859f1460d0a958d924a
Vendor states this is fixed in 011479cf9a7657d4a3e7cc42a784ac63df594170 (fixed)
Vendor states this is fixed in 6f66d38e2a6c78d48723ea17ad86135ec80ca24b (fixed)
Vendor states this is fixed in 8f766d2d0b4dabf54f8b35812df2b4f481d13316 (fixed)
Vendor states this is fixed in 9accc25e5af0bac8479f6054e674b2c593c45281 (fixed)
Vendor states this is fixed in 9d04d64ad192439835ed9884d767353061c3ed6f (fixed)
Vendor states this is fixed in d79d7b9e8acbb53e2d60f6b24afc13e2f15e691f (fixed)
Vendor states this is fixed in edb20e8c03aebacb409968c99d046f509c6c485a (fixed)
Vendor states this is fixed in f6310491c4cdb88af73aa551ec9df1f10a90c709 (fixed)
Vendor states this is fixed in 2.6.19 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card