CVE-2026-72489: staging: nvec: fix use-after-free in nvec_rx_completed()
Noroxi assessment
Priority: Monitor (action score 33/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.19% (FIRST EPSS).
- Someone with local access to the system 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 08626fcfe12308ca3f8b22c538ba7dee0b2dce7a, 26813881181deb3a32fbb59eadb2599cbe8423f6, 5de04caa46b635e180cecbd164e333eca535db94.
Low priority for now. Upgrade to Linux Linux 08626fcfe12308ca3f8b22c538ba7dee0b2dce7a, 26813881181deb3a32fbb59eadb2599cbe8423f6, 5de04caa46b635e180cecbd164e333eca535db94 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: staging: nvec: fix use-after-free in nvec_rx_completed() In nvec_rx_completed(), when an incomplete RX transfer is detected, nvec_msg_free() is called to return the message back to the pool by clearing its 'used' atomic flag. Immediately after this, the code accesses nvec->rx->data[0] to check the message type. Since nvec_msg_free() marks the pool slot as available via atomic_set(), any concurrent or subsequent call to nvec_msg_alloc() could claim that same slot and overwrite its data[] array. Reading nvec->rx->data[0] after freeing the message is therefore a use-after-free. Fix this by saving the message type byte before calling nvec_msg_free(), then using the saved value for the battery quirk check.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- 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
- 3.2affected
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before 6b2ea886ebdae44a2394029844a4e78f58e1587daffected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before a37625c7b688fcf68a54263528eccbabfd7fa17aaffected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before 9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89affected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before 08626fcfe12308ca3f8b22c538ba7dee0b2dce7aaffected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before f19a5bc059051143c489dd6f79a0f9c3bfd13aeaaffected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90affected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before 5de04caa46b635e180cecbd164e333eca535db94affected · git
- d6bdcf2e1019351cbc176e963b7756766bdd8721 and later · before 26813881181deb3a32fbb59eadb2599cbe8423f6affected · git
- before 3.2not 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:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| 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-72484Aug 15, 2026 · staging: most: video: avoid double free on video register failure0Monitor
- ← EarlierCVE-2026-72486Aug 15, 2026 · mailbox: mtk-adsp: fix UAF during device teardown0Monitor
- Later →CVE-2026-72490Aug 15, 2026 · staging: rtl8723bs: fix stainfo check in rtw_aes_decrypt0Monitor
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 | 08626fcfe12308ca3f8b22c538ba7dee0b2dce7a | Vendor (CNA) |
| Linux Linux | 26813881181deb3a32fbb59eadb2599cbe8423f6 | Vendor (CNA) |
| Linux Linux | 5de04caa46b635e180cecbd164e333eca535db94 | Vendor (CNA) |
| Linux Linux | 6b2ea886ebdae44a2394029844a4e78f58e1587d | Vendor (CNA) |
| Linux Linux | 9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89 | Vendor (CNA) |
| Linux Linux | a37625c7b688fcf68a54263528eccbabfd7fa17a | Vendor (CNA) |
| Linux Linux | bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90 | Vendor (CNA) |
| Linux Linux | f19a5bc059051143c489dd6f79a0f9c3bfd13aea | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | 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
- Someone with local access to the system 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
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 (7 more)Show less
- git.kernel.org/stable/c/26813881181deb3a32fbb59eadb2599cbe8423f6
- git.kernel.org/stable/c/5de04caa46b635e180cecbd164e333eca535db94
- git.kernel.org/stable/c/6b2ea886ebdae44a2394029844a4e78f58e1587d
- git.kernel.org/stable/c/9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89
- git.kernel.org/stable/c/a37625c7b688fcf68a54263528eccbabfd7fa17a
- git.kernel.org/stable/c/bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90
- git.kernel.org/stable/c/f19a5bc059051143c489dd6f79a0f9c3bfd13aea
Vendor advisories and official records. Exploit/PoC links are deliberately left out.