CVE-2026-31730: misc: fastrpc: possible double-free of cctx->remote_heap
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.12% (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 0bdee4118340c5a756220c1b29a7dab86bb0aa65, 3a164f640953cc982804746e772d379171aff5c6, 4b8e527aca357a6488680713bd88007cf8f547fe.
Low priority for now. Upgrade to Linux Linux 0bdee4118340c5a756220c1b29a7dab86bb0aa65, 3a164f640953cc982804746e772d379171aff5c6, 4b8e527aca357a6488680713bd88007cf8f547fe 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: misc: fastrpc: possible double-free of cctx->remote_heap fastrpc_init_create_static_process() may free cctx->remote_heap on the err_map path but does not clear the pointer. Later, fastrpc_rpmsg_remove() frees cctx->remote_heap again if it is non-NULL, which can lead to a double-free if the INIT_CREATE_STATIC ioctl hits the error path and the rpmsg device is subsequently removed/unbound. Clear cctx->remote_heap after freeing it in the error path to prevent the later cleanup from freeing it again. This issue was found by an in-house analysis workflow that extracts AST-based information and runs static checks, with LLM assistance for triage, and was confirmed by manual code review. No hardware testing was performed.
- Published
- May 1, 2026
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-415
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.1%
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.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2 and later · before 6.6.134
- linux linux kernel6.7 and later · before 6.12.81
- linux linux kernel6.13 and later · before 6.18.22
- linux linux kernel6.19 and later · before 6.19.12
- linux linux kernel7.0
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
- 0871561055e666da421d779397efcc1e5e964cab and later · before 4b8e527aca357a6488680713bd88007cf8f547feaffected · git
- 0871561055e666da421d779397efcc1e5e964cab and later · before 0bdee4118340c5a756220c1b29a7dab86bb0aa65affected · git
- 0871561055e666da421d779397efcc1e5e964cab and later · before 3a164f640953cc982804746e772d379171aff5c6affected · git
- 0871561055e666da421d779397efcc1e5e964cab and later · before f67d368d26764a357691b2b3a33d3cb55b435bfcaffected · git
- 0871561055e666da421d779397efcc1e5e964cab and later · before ba2c83167b215da30fa2aae56b140198cf8d8408affected · git
- before 6.2not affected · semver
- 6.6.134 and later · up to and including 6.6.*not affected · semver
- 6.12.81 and later · up to and including 6.12.*not affected · semver
- 6.18.22 and later · up to and including 6.18.*not affected · 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.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.12-1 | 6.19.12-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-31727May 1, 2026 · usb: gadget: u_ether: Fix NULL pointer deref in eth_get_drvinfo22Monitor
- ← EarlierCVE-2026-31728May 1, 2026 · usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop18Monitor
- Later →CVE-2026-31732May 1, 2026 · gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()22Monitor
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 | 0bdee4118340c5a756220c1b29a7dab86bb0aa65 | Vendor (CNA) |
| Linux Linux | 3a164f640953cc982804746e772d379171aff5c6 | Vendor (CNA) |
| Linux Linux | 4b8e527aca357a6488680713bd88007cf8f547fe | Vendor (CNA) |
| Linux Linux | ba2c83167b215da30fa2aae56b140198cf8d8408 | Vendor (CNA) |
| Linux Linux | f67d368d26764a357691b2b3a33d3cb55b435bfc | Vendor (CNA) |
| 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.
No history yet (it accumulates with the daily EPSS job).
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.
- CVE-2026-430110 days apartnet/x25: Fix potential double free of skb39Monitor
- CVE-2026-316087 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()39Monitor
- CVE-2026-316097 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()39Monitor
- CVE-2026-434147 days apartscsi: qla2xxx: Completely fix fcport double free39Monitor
- CVE-2026-5299354 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-6388879 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
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
- 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-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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.