CVE-2026-31638: rxrpc: Only put the call ref if one was acquired
Noroxi assessment
Priority: Monitor (action score 30/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.44% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 0c156aff8a2d4fa0d61db7837641975cf0e5452d, 6331f1b24a3e85465f6454e003a3e6c22005a5c5, 8299ca146489664e3c0c90a3b8900d8335b1ede4; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1.
Low priority for now. Upgrade to Linux Linux 0c156aff8a2d4fa0d61db7837641975cf0e5452d, 6331f1b24a3e85465f6454e003a3e6c22005a5c5, 8299ca146489664e3c0c90a3b8900d8335b1ede4; azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 6.6.137.1-1 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: rxrpc: Only put the call ref if one was acquired rxrpc_input_packet_on_conn() can process a to-client packet after the current client call on the channel has already been torn down. In that case chan->call is NULL, rxrpc_try_get_call() returns NULL and there is no reference to drop. The client-side implicit-end error path does not account for that and unconditionally calls rxrpc_put_call(). This turns a protocol error path into a kernel crash instead of rejecting the packet. Only drop the call reference if one was actually acquired. Keep the existing protocol error handling unchanged.
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-476
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Is your version affected? Check itNoroxi 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 |
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
- 6.2affected
- 5e6ef4f1017c7f844e305283bbd8875af475e2fc and later · before b8f66447448d6c305a51413a67ec8ed26aa7d1ddaffected · git
- 5e6ef4f1017c7f844e305283bbd8875af475e2fc and later · before 0c156aff8a2d4fa0d61db7837641975cf0e5452daffected · git
- 5e6ef4f1017c7f844e305283bbd8875af475e2fc and later · before 8299ca146489664e3c0c90a3b8900d8335b1ede4affected · git
- 5e6ef4f1017c7f844e305283bbd8875af475e2fc and later · before 9fb09861e2b8d1abfe2efaf260c9f1d30080ea38affected · git
- 5e6ef4f1017c7f844e305283bbd8875af475e2fc and later · before 6331f1b24a3e85465f6454e003a3e6c22005a5c5affected · git
- before 6.2not affected · semver
- 6.6.135 and later · up to and including 6.6.*not affected · semver
- 6.12.82 and later · up to and including 6.12.*not affected · semver
- 6.18.23 and later · up to and including 6.18.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2.1 and later · before 6.6.135
- linux linux kernel6.7 and later · before 6.12.82
- linux linux kernel6.13 and later · before 6.18.23
- linux linux kernel6.19 and later · before 6.19.13
- linux linux kernel6.2
- linux linux kernel7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.13-1 | 6.19.13-1 |
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-2026-31636Apr 24, 2026 · rxrpc: fix RESPONSE authenticator parser OOB read36Monitor
- ← EarlierCVE-2026-31637Apr 24, 2026 · rxrpc: reject undecryptable rxkad response tickets39Monitor
- Later →CVE-2026-31639Apr 24, 2026 · rxrpc: Fix key reference count leak from call->key22Monitor
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 | 0c156aff8a2d4fa0d61db7837641975cf0e5452d | Vendor (CNA) |
| Linux Linux | 6331f1b24a3e85465f6454e003a3e6c22005a5c5 | Vendor (CNA) |
| Linux Linux | 8299ca146489664e3c0c90a3b8900d8335b1ede4 | Vendor (CNA) |
| Linux Linux | 9fb09861e2b8d1abfe2efaf260c9f1d30080ea38 | Vendor (CNA) |
| Linux Linux | b8f66447448d6c305a51413a67ec8ed26aa7d1dd | Vendor (CNA) |
| azl3 kernel 6.6.134.1-2 on Azure Linux 3.0 | 6.6.137.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.85-1 · Debian:13 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.