{"api_version":"1","generated_at":"2026-09-27T03:01:55+00:00","cve":"CVE-2026-97916","urls":{"html":"https://cve.report/CVE-2026-97916","api":"https://cve.report/api/cve/CVE-2026-97916.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97916","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97916"},"summary":{"title":"accel/ivpu: Validate firmware log buffer metadata","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Validate firmware log buffer metadata\n\nThe tracing log headers parsed by fw_log_print_buffer() reside in\nDMA-shared BOs that the NPU firmware can write to.\n\nfw_log_from_bo() validated log->header_size and log->size, but\nfw_log_print_buffer() re-read those same fields from shared memory\nafterwards, allowing a TOCTOU where firmware changes them between the\ncheck and the use, and making the host dereference out-of-bounds\naddresses while printing logs.\n\nSnapshot the validated values once with READ_ONCE() and pass them down\nexplicitly in a new struct ivpu_fw_log_desc instead of re-reading them\nfrom the shared struct.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:18","updated_at":"2026-09-25 11:17:18"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b1555f63ee1a680f280bc18e8dac416f250e2ec3","name":"https://git.kernel.org/stable/c/b1555f63ee1a680f280bc18e8dac416f250e2ec3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/40868f80a89199630b03d4457876f9a1feba0660","name":"https://git.kernel.org/stable/c/40868f80a89199630b03d4457876f9a1feba0660","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0724afc55c77c36c7feb9a7264b02aa7593c5c2d","name":"https://git.kernel.org/stable/c/0724afc55c77c36c7feb9a7264b02aa7593c5c2d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8ec3d6972f1440fae6c8dadd1859892775208759","name":"https://git.kernel.org/stable/c/8ec3d6972f1440fae6c8dadd1859892775208759","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97916","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97916","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 8ec3d6972f1440fae6c8dadd1859892775208759 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 40868f80a89199630b03d4457876f9a1feba0660 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 b1555f63ee1a680f280bc18e8dac416f250e2ec3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected d4e4257afa6ed5205eda993180401fc2c20e4b60 0724afc55c77c36c7feb9a7264b02aa7593c5c2d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"97916","cve":"CVE-2026-97916","epss":"0.002000000","percentile":"0.088390000","score_date":"2026-09-26","updated_at":"2026-09-27 00:04:20"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/accel/ivpu/ivpu_fw_log.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"8ec3d6972f1440fae6c8dadd1859892775208759","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"40868f80a89199630b03d4457876f9a1feba0660","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"b1555f63ee1a680f280bc18e8dac416f250e2ec3","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"},{"lessThan":"0724afc55c77c36c7feb9a7264b02aa7593c5c2d","status":"affected","version":"d4e4257afa6ed5205eda993180401fc2c20e4b60","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/accel/ivpu/ivpu_fw_log.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.6"},{"lessThan":"6.6","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.6","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc3","versionStartIncluding":"6.6","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Validate firmware log buffer metadata\n\nThe tracing log headers parsed by fw_log_print_buffer() reside in\nDMA-shared BOs that the NPU firmware can write to.\n\nfw_log_from_bo() validated log->header_size and log->size, but\nfw_log_print_buffer() re-read those same fields from shared memory\nafterwards, allowing a TOCTOU where firmware changes them between the\ncheck and the use, and making the host dereference out-of-bounds\naddresses while printing logs.\n\nSnapshot the validated values once with READ_ONCE() and pass them down\nexplicitly in a new struct ivpu_fw_log_desc instead of re-reading them\nfrom the shared struct."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:22:37.699Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/8ec3d6972f1440fae6c8dadd1859892775208759"},{"url":"https://git.kernel.org/stable/c/40868f80a89199630b03d4457876f9a1feba0660"},{"url":"https://git.kernel.org/stable/c/b1555f63ee1a680f280bc18e8dac416f250e2ec3"},{"url":"https://git.kernel.org/stable/c/0724afc55c77c36c7feb9a7264b02aa7593c5c2d"}],"title":"accel/ivpu: Validate firmware log buffer metadata","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97916","datePublished":"2026-09-25T10:22:37.699Z","dateReserved":"2026-09-25T10:18:58.201Z","dateUpdated":"2026-09-25T10:22:37.699Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:18","lastModifiedDate":"2026-09-25 11:17:18","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97916","Ordinal":"1","Title":"accel/ivpu: Validate firmware log buffer metadata","CVE":"CVE-2026-97916","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97916","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/ivpu: Validate firmware log buffer metadata\n\nThe tracing log headers parsed by fw_log_print_buffer() reside in\nDMA-shared BOs that the NPU firmware can write to.\n\nfw_log_from_bo() validated log->header_size and log->size, but\nfw_log_print_buffer() re-read those same fields from shared memory\nafterwards, allowing a TOCTOU where firmware changes them between the\ncheck and the use, and making the host dereference out-of-bounds\naddresses while printing logs.\n\nSnapshot the validated values once with READ_ONCE() and pass them down\nexplicitly in a new struct ivpu_fw_log_desc instead of re-reading them\nfrom the shared struct.","Type":"Description","Title":"accel/ivpu: Validate firmware log buffer metadata"}]}}}