{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74403 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74403 is a high-severity 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-74403 and fix it if it is affected.\n\nWhat it is: CVE-2026-74403 is a high-severity 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-74403 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-74403/ (Markdown: https://insights.sbomify.com/CVE-2026-74403/index.md)","id":"CVE-2026-74403","markdown":"https://insights.sbomify.com/CVE-2026-74403/index.md","name":"CVE-2026-74403","record":{"aliases":["DEBIAN-CVE-2026-74403","GHSA-6wq7-xhx5-p3vw","UBUNTU-CVE-2026-74403"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A missing null check in the Linux kernel's CCP driver can lead to a kernel crash when memory allocation fails during TIO initialization.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: ccp - Check for page allocation failure correctly in TIO\n\nSashiko notes:\n\n\u003e if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it\n\u003e safe to pass it directly to page_address()?\n\u003e\n\u003e On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might\n\u003e compute a deterministic but invalid, non-zero virtual address. The\n\u003e subsequent if (tio_status) check would then evaluate to true, and\n\u003e sev_tsm_init_locked() would dereference the invalid pointer.\n\nIndeed, page_address(NULL) will return non-NULL garbage here. Fix this by\nchecking the page allocation itself for NULL, not the resulting virtual\naddress.","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: ccp - Check for page allocation failure correctly in TIO","id":"CVE-2026-74403","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one","id":"CVE-2026-74404"},"packages":[],"prev":{"headline":"crypto: atmel-sha204a - fix blocking and non-blocking rng logic","id":"CVE-2026-74402"},"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 missing null check in the Linux kernel's CCP driver can lead to a kernel crash when memory allocation fails during TIO initialization.","url":"https://insights.sbomify.com/CVE-2026-74403/"}