CVE-2026-93163: hwrng: core - fix rng list on registration error
Noroxi assessment
Priority: Monitor (action score 0/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.21% (FIRST EPSS).
- Fixed version: Linux Linux 30b2cc2966dac87ee95a99c49e28486c2a8129cd, 3a5834db2b1ce25649f330e78efe1ccde78967fd, 4.10.
Low priority for now. Upgrade to Linux Linux 30b2cc2966dac87ee95a99c49e28486c2a8129cd, 3a5834db2b1ce25649f330e78efe1ccde78967fd, 4.10 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: hwrng: core - fix rng list on registration error hwrng_register(rng) does the following: 1. Checks if rng has name and read methods set 2. Checks if the name already exists 3. Adds rng to global rng_list 4. May try to set rng to current_rng If step 4 fails, it returns an error. However, it does not remove the rng from rng_list, causing a dangling reference which can result in use-after-free if the caller frees rng, since registration failed. Add a list_del_init() cleanup step.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 42802952a2725f85f7e36ee3b29593af5fe87197, 4.14affected
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before 30b2cc2966dac87ee95a99c49e28486c2a8129cdaffected · git
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before e37c67f768234e14cd6ea3b081568dd915c5b67eaffected · git
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before de4f1bcb61a73cc896decdbd27d61a34add93b53affected · git
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before cf293c9c7424de0d04b51367d07f40570ce80231affected · git
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before bee8d1fcdc8f389b595b0a4cf6fe8440f499458aaffected · git
- 2bbb6983887fefc8026beab01198d30f47b7bd22 and later · before 3a5834db2b1ce25649f330e78efe1ccde78967fdaffected · git
- 4.9.320 and later · before 4.10affected · semver
- before 4.14not affected · semver
- 6.1.191 and later · up to and including 6.1.*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:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-93161Sep 17, 2026 · crypto: qat - clear AES key schedule from stack0Monitor
- ← EarlierCVE-2026-93162Sep 17, 2026 · crypto: qat - cancel work on re-enable SR-IOV timeout0Monitor
- Later →CVE-2026-93164Sep 17, 2026 · uprobes/x86: Move optimized uprobe from nop5 to nop100Monitor
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 | 30b2cc2966dac87ee95a99c49e28486c2a8129cd | Vendor (CNA) |
| Linux Linux | 3a5834db2b1ce25649f330e78efe1ccde78967fd | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | bee8d1fcdc8f389b595b0a4cf6fe8440f499458a | Vendor (CNA) |
| Linux Linux | cf293c9c7424de0d04b51367d07f40570ce80231 | Vendor (CNA) |
| Linux Linux | de4f1bcb61a73cc896decdbd27d61a34add93b53 | Vendor (CNA) |
| Linux Linux | e37c67f768234e14cd6ea3b081568dd915c5b67e | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3a5834db2b1ce25649f330e78efe1ccde78967fd
- git.kernel.org/stable/c/bee8d1fcdc8f389b595b0a4cf6fe8440f499458a
- git.kernel.org/stable/c/cf293c9c7424de0d04b51367d07f40570ce80231
- git.kernel.org/stable/c/de4f1bcb61a73cc896decdbd27d61a34add93b53
- git.kernel.org/stable/c/e37c67f768234e14cd6ea3b081568dd915c5b67e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.