{"api_version":"1","generated_at":"2026-09-09T06:55:18+00:00","cve":"CVE-2026-80835","urls":{"html":"https://cve.report/CVE-2026-80835","api":"https://cve.report/api/cve/CVE-2026-80835.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80835","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80835"},"summary":{"title":"crypto: qcom-rng - Remove crypto_rng interface","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - Remove crypto_rng interface\n\nqcom-rng.c exposes the same hardware through two completely separate\ninterfaces, crypto_rng and hwrng.  However, the implementation of this\nis buggy because it permits generation operations from these interfaces\nto run concurrently with each other, accessing the same registers.  That\nis, qcom_rng_generate() synchronizes with itself but not with\nqcom_hwrng_read().  This results in potential repetition of output from\nthe RNG, output of non-random values, etc.\n\nFortunately, there's actually no point in hardware RNG drivers\nimplementing the crypto_rng interface.  It's not actually used by\nanything besides the \"rng\" algorithm type of AF_ALG, which in turn is\nnot actually used in practice.  Other crypto_rng hardware drivers are\nlikewise being phased out, leaving just the hwrng support.\n\nThus, remove it to simplify the code and avoid conflict (and confusion)\nwith the hwrng interface which is the one that actually matters.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:11","updated_at":"2026-09-04 16:18:11"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d","name":"https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0","name":"https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2","name":"https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b","name":"https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f","name":"https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80835","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80835","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f29cd5bb64c258f29b4c49452532481f50eb43ca bb474dcd9d0224264a27a60891f00872b879835f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f29cd5bb64c258f29b4c49452532481f50eb43ca 14d9ee8286460a7b82f3b8610b5c7ebf4550b06b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f29cd5bb64c258f29b4c49452532481f50eb43ca 843e2bdaf8deb8bc341203094dfe582e38ea4af2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f29cd5bb64c258f29b4c49452532481f50eb43ca 669d940351eda316b82e24986e2e0e057653ce7d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f29cd5bb64c258f29b4c49452532481f50eb43ca 2ecdf5c9910e20f73639bc322f0518a3439d17c0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.108 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.49 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.13 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.3 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80835","cve":"CVE-2026-80835","epss":"0.001680000","percentile":"0.063410000","score_date":"2026-09-07","updated_at":"2026-09-08 00:05:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/crypto/Kconfig","drivers/crypto/qcom-rng.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"bb474dcd9d0224264a27a60891f00872b879835f","status":"affected","version":"f29cd5bb64c258f29b4c49452532481f50eb43ca","versionType":"git"},{"lessThan":"14d9ee8286460a7b82f3b8610b5c7ebf4550b06b","status":"affected","version":"f29cd5bb64c258f29b4c49452532481f50eb43ca","versionType":"git"},{"lessThan":"843e2bdaf8deb8bc341203094dfe582e38ea4af2","status":"affected","version":"f29cd5bb64c258f29b4c49452532481f50eb43ca","versionType":"git"},{"lessThan":"669d940351eda316b82e24986e2e0e057653ce7d","status":"affected","version":"f29cd5bb64c258f29b4c49452532481f50eb43ca","versionType":"git"},{"lessThan":"2ecdf5c9910e20f73639bc322f0518a3439d17c0","status":"affected","version":"f29cd5bb64c258f29b4c49452532481f50eb43ca","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/crypto/Kconfig","drivers/crypto/qcom-rng.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.108","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.49","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.13","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.3","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.108","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.49","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.13","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.3","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - Remove crypto_rng interface\n\nqcom-rng.c exposes the same hardware through two completely separate\ninterfaces, crypto_rng and hwrng.  However, the implementation of this\nis buggy because it permits generation operations from these interfaces\nto run concurrently with each other, accessing the same registers.  That\nis, qcom_rng_generate() synchronizes with itself but not with\nqcom_hwrng_read().  This results in potential repetition of output from\nthe RNG, output of non-random values, etc.\n\nFortunately, there's actually no point in hardware RNG drivers\nimplementing the crypto_rng interface.  It's not actually used by\nanything besides the \"rng\" algorithm type of AF_ALG, which in turn is\nnot actually used in practice.  Other crypto_rng hardware drivers are\nlikewise being phased out, leaving just the hwrng support.\n\nThus, remove it to simplify the code and avoid conflict (and confusion)\nwith the hwrng interface which is the one that actually matters."}],"providerMetadata":{"dateUpdated":"2026-09-04T15:54:44.116Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/bb474dcd9d0224264a27a60891f00872b879835f"},{"url":"https://git.kernel.org/stable/c/14d9ee8286460a7b82f3b8610b5c7ebf4550b06b"},{"url":"https://git.kernel.org/stable/c/843e2bdaf8deb8bc341203094dfe582e38ea4af2"},{"url":"https://git.kernel.org/stable/c/669d940351eda316b82e24986e2e0e057653ce7d"},{"url":"https://git.kernel.org/stable/c/2ecdf5c9910e20f73639bc322f0518a3439d17c0"}],"title":"crypto: qcom-rng - Remove crypto_rng interface","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80835","datePublished":"2026-09-04T15:54:44.116Z","dateReserved":"2026-08-26T14:34:25.796Z","dateUpdated":"2026-09-04T15:54:44.116Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:11","lastModifiedDate":"2026-09-04 16:18:11","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80835","Ordinal":"1","Title":"crypto: qcom-rng - Remove crypto_rng interface","CVE":"CVE-2026-80835","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80835","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: qcom-rng - Remove crypto_rng interface\n\nqcom-rng.c exposes the same hardware through two completely separate\ninterfaces, crypto_rng and hwrng.  However, the implementation of this\nis buggy because it permits generation operations from these interfaces\nto run concurrently with each other, accessing the same registers.  That\nis, qcom_rng_generate() synchronizes with itself but not with\nqcom_hwrng_read().  This results in potential repetition of output from\nthe RNG, output of non-random values, etc.\n\nFortunately, there's actually no point in hardware RNG drivers\nimplementing the crypto_rng interface.  It's not actually used by\nanything besides the \"rng\" algorithm type of AF_ALG, which in turn is\nnot actually used in practice.  Other crypto_rng hardware drivers are\nlikewise being phased out, leaving just the hwrng support.\n\nThus, remove it to simplify the code and avoid conflict (and confusion)\nwith the hwrng interface which is the one that actually matters.","Type":"Description","Title":"crypto: qcom-rng - Remove crypto_rng interface"}]}}}