{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-97433", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-97433" ], "published": "2026-09-24T16:08:25Z", "summary": "nvme: validate FDP configuration descriptor sizes", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme: validate FDP configuration descriptor sizes\n\nValidate descriptor sizes while walking the FDP configurations log so\ndsze == 0 or a descriptor past the log end cannot cause unbounded\niteration or reads past the buffer.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.29-1+rpt1", "1:6.18.33-1+rpt1", "1:6.18.34-1+rpt1", "1:6.18.39-1+rpt1", "1:6.18.50-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.29+rpt-rpi-2712", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-2712", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-2712", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.50+rpt-rpi-2712", "binary_version": "1:6.18.50-1+rpt1" }, { "binary_name": "linux-image-6.18.50+rpt-rpi-v8", "binary_version": "1:6.18.50-1+rpt1" }, { "binary_name": "linux-image-6.18.50+rpt-rpi-v8-rt", "binary_version": "1:6.18.50-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.29-1+rpt1": { "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc", "upstream_version": "6.18.29", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.53" }, "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.53" }, "1:6.18.34-1+rpt1": { "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af", "upstream_version": "6.18.34", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.53" }, "1:6.18.39-1+rpt1": { "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff", "upstream_version": "6.18.39", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.53" }, "1:6.18.50-1+rpt1": { "linux_commit": "cff533aec2fa601846766b32ff57204e0a61bed7", "upstream_version": "6.18.50", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.53" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-97433" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/97efd7a41aac08b43ea2337c5913a2bc75484f9f" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/0ef4daa6534a510d61ea67c8ad9bb5097b0dd5f8" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-09-25T12:45:48Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.2, "cvss_v3_severity": "High", "scenario": "AV:N - nvme_query_fdp_granularity() walks nvme_fdp_config_desc.dsze from the Get Log Page LID 0x20 (NVME_LOG_FDP_CONFIGS) buffer filled by nvme_get_log_lsi(); on nvme-tcp that payload is C2HData copied by nvme_tcp_recv_data() from the remote NVMe-oF target (TCP 4420), so the malformed descriptor sizes arrive on the wire.\nAC:L - The peer sets Identify ctratt NVME_CTRL_ATTR_FDPS, Get Features FID 0x1d (FDPE and fdpcidx), and log fields sze/dsze, so nvme_query_fdp_granularity() can skip with a crafted dsze to park desc just below end and then load nrg/runs past the kvmalloc object with no race.\nPR:N - The attacker is the NVMe-oF controller. nvme_scan_work() submits that Get Log Page on the existing admin_q; DH-HMAC-CHAP and TLS are optional, and no host uid, capability, or /dev/nvme-fabrics write is required once the session exists.\nUI:N - nvme_start_ctrl() queues ctrl->scan_work and nvme_handle_aen_notice() requeues it on NVME_AER_NOTICE_NS_CHANGED, so nvme_scan_ns()->nvme_update_ns_info_block()->nvme_query_fdp_info()->nvme_query_fdp_granularity() runs on nvme_wq without a further victim mount or click.\nS:U - The over-read is of the host kvmalloc FDP configs log and the info->runs store inside nvme_query_fdp_granularity(); it does not cross a KVM/Xen, IOMMU, or other distinct security authority.\nC:L - After the dsze walk, nvme_query_fdp_granularity() only does le32_to_cpu(desc->nrg) and le64_to_cpu(desc->runs) (offsets 4 and 16). With desc at end-1 that is a strictly bounded 12-byte load past the log object, a small heap leak rather than an arbitrary read.\nI:N - Those fields are stored to info->runs and min()'d into write_stream_granularity in nvme_update_ns_info_block(); the dsze walk performs no out-of-bounds write, use-after-free, or control-flow hijack.\nA:H - hdr.sze is attacker-chosen (capped at PAGE_SIZE*MAX_ORDER_NR_PAGES) for kvmalloc(), and desc->nrg/desc->runs are then loaded without ensuring the selected descriptor fits; that over-read past the allocation can oops when the walk parks desc at the buffer end." } } }