{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98362 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98362 is a memory corruption vulnerability in Linux, published on 6 Oct 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-98362 and fix it if it is affected.\n\nWhat it is: CVE-2026-98362 is a memory corruption vulnerability in Linux, published on 6 Oct 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-98362 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-98362/ (Markdown: https://insights.sbomify.com/CVE-2026-98362/index.md)","id":"CVE-2026-98362","markdown":"https://insights.sbomify.com/CVE-2026-98362/index.md","name":"CVE-2026-98362","record":{"aliases":["AZL-106020","BELL-CVE-2026-98362","DEBIAN-CVE-2026-98362","GHSA-q57h-9f6r-c5h9","UBUNTU-CVE-2026-98362"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A missing upper bound check in the Linux kernel SCPI clock driver allows out-of-bounds memory access, potentially causing crashes or information leaks.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nclk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate\n\ndvfs_get_idx() may return an out-of-range index if the SCP firmware is\nbuggy or returns a stale value. Only negative indexes were rejected, so a\nlarge index walked past info-\u003eopps and could treat garbage as a clock rate\n(KASAN OOB / wrong frequency to consumers). The missing upper bound dates\nback to the original SCPI clock driver.\n\nTreat indexes \u003e= opp count as invalid and return 0, same as idx \u003c 0.","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":"clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate","id":"CVE-2026-98362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"firmware: arm_scpi: reject DVFS OPP count above MAX_DVFS_OPPS","id":"CVE-2026-98363"},"packages":[],"prev":{"headline":"RDMA/rxe: Restore HMM_PFN_WRITE check in ODP write paths","id":"CVE-2026-98361"},"products":["Linux"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A missing upper bound check in the Linux kernel SCPI clock driver allows out-of-bounds memory access, potentially causing crashes or information leaks.","url":"https://insights.sbomify.com/CVE-2026-98362/"}