{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74438 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74438 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74438 and fix it if it is affected.\n\nWhat it is: CVE-2026-74438 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74438 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74438/ (Markdown: https://insights.sbomify.com/CVE-2026-74438/index.md)","id":"CVE-2026-74438","markdown":"https://insights.sbomify.com/CVE-2026-74438/index.md","name":"CVE-2026-74438","record":{"aliases":["BELL-CVE-2026-74438","DEBIAN-CVE-2026-74438","GHSA-pqhh-48h7-jg73","UBUNTU-CVE-2026-74438"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel crypto","requires_auth":"low_privilege","summary":"A buffer overflow in the unused sun4i-ss random number generator allows potential code execution or denial of service, fixed by removing the insecure code.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: sun4i-ss - Remove insecure and unused rng_alg\n\nRemove sun4i_ss_rng, as it is insecure and unused:\n\n- It has multiple vulnerabilities.  sun4i_ss_prng_seed() is missing\n  locking and has a buffer overflow.  sun4i_ss_prng_generate() fails to\n  fill the entire buffer with cryptographic random bytes, because it\n  rounds the destination length down and also doesn't actually wait for\n  the hardware to be ready before pulling bytes from it.\n\n- No user of this code is known.  It's usable only theoretically via the\n  \"rng\" algorithm type of AF_ALG.  But userspace actually just uses the\n  actual Linux RNG (/dev/random etc) instead.  And rng_algs don't\n  contribute entropy to the actual Linux RNG either.  (This may have\n  been confused with hwrng, which does contribute entropy.)\n\nThe sun4i_ss_prng_seed() buffer overflow was reported by Tianchu Chen\nand discovered by Atuin - Automated Vulnerability Discovery Engine\n\nThere's no point in fixing all these vulnerabilities individually when\nthis is unused code, so let's just remove it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: sun4i-ss - Remove insecure and unused rng_alg","id":"CVE-2026-74438","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry","id":"CVE-2026-74439"},"packages":[],"prev":{"headline":"media: uvcvideo: Fix deadlock if uvc_status_stop is called from async_ctrl.work","id":"CVE-2026-74437"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A buffer overflow in the unused sun4i-ss random number generator allows potential code execution or denial of service, fixed by removing the insecure code.","url":"https://insights.sbomify.com/CVE-2026-74438/"}