CVE-2026-74435: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc
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.63% (FIRST EPSS); higher than 50.1% of all records.
- 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.
- Fixed version: Linux Linux 16c8ae9735c5bd7e54dd7478d6348e0fc860842d, 6.12.97, 6.18.40.
Low priority for now. Upgrade to Linux Linux 16c8ae9735c5bd7e54dd7478d6348e0fc860842d, 6.12.97, 6.18.40 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: rxrpc_verify_data ensure rx_dec_buffer alloc rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the rxrpc_call.rx_dec_buffer is unallocated and assumes that upon successful return that rx_dec_buffer must be allocated. However, rxrpc_verify_data() does not request an allocation if the rxrpc_skb_priv.len is zero. In addition, failure to allocate rx_dec_buffer will result in a call to skb_copy_bits() with a NULL destination which can trigger a NULL pointer dereference. To prevent these issues rxrpc_verify_data() is modified to always attempt to allocate the rxrpc_call.rx_dec_buffer if it is NULL. This issue was identified with assistance of a private sashiko instance.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
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.
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.
—
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
- c580087743712112778a06d65a4074053072d7bf, 7.1affected
- a05bf6d9e621fa71e89ccebe3047ba45218d7b38 and later · before 8bbede0afced346b24e4fbde0c68cf12980ba948affected · git
- b94a6ccbaf1104dd980150a65fdeb2f69d17d2f5 and later · before 6563b4eb38c35d75892445bcf8aacdc29914821caffected · git
- 46cb765e2e5ad52303ea157e10d370bb6b7acbbf and later · before d3b642cf95d48234590cc91450d8705a9bf6b540affected · git
- d2bc90cf6c75cb96d2ce549be6c35efa3099d25b and later · before a962bc8508592c4d51092edac68579bd8b18fe44affected · git
- d2bc90cf6c75cb96d2ce549be6c35efa3099d25b and later · before 16c8ae9735c5bd7e54dd7478d6348e0fc860842daffected · git
- 6.6.143 and later · before 6.6.145affected · semver
- 6.12.93 and later · before 6.12.97affected · semver
- 6.18.35 and later · before 6.18.40affected · semver
- 7.0.11 and later · before 7.1affected · semver
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.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74433Aug 15, 2026 · rxrpc: Fix UAF in rxgk_issue_challenge()39Monitor
- ← EarlierCVE-2026-74434Aug 15, 2026 · rxrpc: Don't move a peeked OOB message onto the pending queue39Monitor
- Later →CVE-2026-74437Aug 15, 2026 · media: uvcvideo: Fix deadlock if uvc_status_stop is called from async_ctrl.work0Monitor
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 | 16c8ae9735c5bd7e54dd7478d6348e0fc860842d | Vendor (CNA) |
| Linux Linux | 6.12.97 | Vendor (CNA) |
| Linux Linux | 6.18.40 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 6563b4eb38c35d75892445bcf8aacdc29914821c | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | 8bbede0afced346b24e4fbde0c68cf12980ba948 | Vendor (CNA) |
| Linux Linux | a962bc8508592c4d51092edac68579bd8b18fe44 | Vendor (CNA) |
| Linux Linux | d3b642cf95d48234590cc91450d8705a9bf6b540 | Vendor (CNA) |
| debian:linux | 6.12.100-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.
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).
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)
—
CVSS 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
- 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.