crypto: qcom-rng - Allow zero as a random number
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.15% (FIRST EPSS).
- Fixed version: Linux Linux 143c74034a1c47b0a1a64e7ca7153e7739bd1244, 3c7101cfc52e378bcb0a46962145e39c9051dd5d, 4c0018320942003bfedd0a1c4cce3f036d363a7f.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 143c74034a1c47b0a1a64e7ca7153e7739bd1244, 3c7101cfc52e378bcb0a46962145e39c9051dd5d, 4c0018320942003bfedd0a1c4cce3f036d363a7f 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: crypto: qcom-rng - Allow zero as a random number Zero is a valid random number and needs to be allowed. Otherwise the output is distinguishable from random.
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- 6.7affected
- f29cd5bb64c258f29b4c49452532481f50eb43ca and later · before 813e6718a199befc4f26f54bdd899fbfa11515e5affected · git
- f29cd5bb64c258f29b4c49452532481f50eb43ca and later · before 4c0018320942003bfedd0a1c4cce3f036d363a7faffected · git
- f29cd5bb64c258f29b4c49452532481f50eb43ca and later · before 143c74034a1c47b0a1a64e7ca7153e7739bd1244affected · git
- f29cd5bb64c258f29b4c49452532481f50eb43ca and later · before 3c7101cfc52e378bcb0a46962145e39c9051dd5daffected · git
- f29cd5bb64c258f29b4c49452532481f50eb43ca and later · before 4ef04bdc0c9f98836d1638be516f6bf1bad55f69affected · git
- before 6.7not affected · semver
- 6.12.108 and later · up to and including 6.12.*not affected · semver
- 6.18.49 and later · up to and including 6.18.*not affected · semver
- 7.1.13 and later · up to and including 7.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-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.1.13-1 | 7.1.13-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
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
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 | 143c74034a1c47b0a1a64e7ca7153e7739bd1244 | Vendor (CNA) |
| Linux Linux | 3c7101cfc52e378bcb0a46962145e39c9051dd5d | Vendor (CNA) |
| Linux Linux | 4c0018320942003bfedd0a1c4cce3f036d363a7f | Vendor (CNA) |
| Linux Linux | 4ef04bdc0c9f98836d1638be516f6bf1bad55f69 | Vendor (CNA) |
| Linux Linux | 813e6718a199befc4f26f54bdd899fbfa11515e5 | Vendor (CNA) |
| 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).
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1059 · Sep 10, 2026(Linux Kernel Güvenlik Bildirimi)
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
- 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.