{ "affected": [ { "ranges": [ { "events": [ { "introduced": "f9c589e142d04b8a19eb382162f804d17102b5ed" }, { "fixed": "c8124b28f12dbdd126118e63d0ebf8093a01fb81" }, { "fixed": "e04d5304a248e5d2a7f4faa87541644bdd320cfb" }, { "fixed": "a1629dfb011446d02905778f6df19f14c5f4f3b3" }, { "fixed": "43239fc6dfb62c50ae1b9c0e82bac0f8cd2e285c" }, { "fixed": "3c9a2b5a4f1183696f02ac280ced1d34afb409b1" }, { "fixed": "efaab8938fb92979be6df359f7d1a43fb7e4717d" }, { "fixed": "7236bbd2cb7d9fc0eda896bbd34790341e2a4377" }, { "fixed": "ff44dfb03a293bf30e31f98772a1dd316a6071d1" } ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "type": "GIT" } ] }, { "package": { "ecosystem": "Linux", "name": "Kernel" }, "ranges": [ { "events": [ { "introduced": "4.8.0" }, { "fixed": "5.10.270" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "5.11.0" }, { "fixed": "5.15.221" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "5.16.0" }, { "fixed": "6.1.188" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "6.2.0" }, { "fixed": "6.6.157" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "6.7.0" }, { "fixed": "6.12.110" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "6.13.0" }, { "fixed": "6.18.51" } ], "type": "ECOSYSTEM" }, { "events": [ { "introduced": "6.19.0" }, { "fixed": "7.2.5" } ], "type": "ECOSYSTEM" } ] } ], "database_specific": { "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90015.json" }, "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxhci: fix lost bounce buffers on TDs spanning several ring segments\n\nWhen a TD reaches a link TRB with data that is not aligned to the\nendpoint's wMaxPacketSize, xhci_align_td() stages the unalignable tail\nthrough the bounce buffer of the ring segment holding that link TRB.\nxhci_unmap_td_bounce_buffer() later unmaps it and, for IN transfers,\ncopies the data back into the URB's buffer.\n\nThe enqueue path records the segment that was bounced in td-\u003ebounce_seg,\nunder the assumption that a TD never spans more than two ring segments.\nThat assumption does not hold: a TD large enough to span three or more\nsegments crosses several link TRBs and can be bounced at each of them.\nOnly the last one survives in td-\u003ebounce_seg, so every earlier bounce\nbuffer is neither copied back nor DMA unmapped.\n\nThe URB still completes with actual_length equal to the requested length\nand no error, so the transfer looks successful while a wMaxPacketSize\nsized hole in the destination buffer silently keeps its previous\ncontents. It also leaks a DMA mapping per dropped bounce.\n\nAny sufficiently large and fragmented bulk transfer can hit this. It was\nfound with a USB mass storage device behind xHCI backing a dm-verity\ntarget with 512 byte hash blocks, where the stale data is detected rather\nthan silently consumed. The device enumerates as SuperSpeed, so\nwMaxPacketSize is 1024, while dm-bufio issues one 512 byte bio per hash\nblock. verity_prefetch_io() makes the block layer merge hundreds of them\ninto a single request of up to 512 scatterlist entries of 512 bytes each.\nAt 256 TRBs per ring segment such a TD spans three segments, and every\nsegment boundary falls on an odd multiple of 512, i.e. unaligned to\nwMaxPacketSize. dm-bufio then caches a hash block holding stale data and\ndm-verity declares the metadata block corrupted:\n\n device-mapper: verity: 8:2: metadata block 10850 is corrupted\n\nA reproducer running this under qemu is available at\nhttps://github.com/baloo/xhci-verity\n\nThe bounce state (bounce_buf, bounce_dma, bounce_len, bounce_offs)\nalready lives on the ring segment, so there is nothing extra to track.\nKeep recording the last bounced segment in td-\u003ebounce_seg and, on\ncompletion, walk the segments from td-\u003estart_seg up to it, unmapping\nevery segment that still has a pending bounce.\n\nStopping at td-\u003ebounce_seg rather than td-\u003eend_seg matters: a bounce\nimplies the TD continues past that segment's link TRB, so bounce_seg is\nalways strictly before end_seg, and a later TD may already have started\nin end_seg and been bounced there. Walking that far would copy a foreign\nbounce buffer into this URB and unmap it twice. It also keeps the walk\ncorrect if a TD ever wraps the whole ring so that end_seg == start_seg.\n\n[mn: Add ring-\u003enum_segs check to prevent unlikely infinite for loop.]", "id": "CVE-2026-90015", "modified": "2026-09-18T03:30:38.145821003Z", "published": "2026-09-16T10:33:21.471Z", "references": [ { "type": "WEB", "url": "https://git.kernel.org/stable/c/3c9a2b5a4f1183696f02ac280ced1d34afb409b1" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/43239fc6dfb62c50ae1b9c0e82bac0f8cd2e285c" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/7236bbd2cb7d9fc0eda896bbd34790341e2a4377" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/a1629dfb011446d02905778f6df19f14c5f4f3b3" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/c8124b28f12dbdd126118e63d0ebf8093a01fb81" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/e04d5304a248e5d2a7f4faa87541644bdd320cfb" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/efaab8938fb92979be6df359f7d1a43fb7e4717d" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/ff44dfb03a293bf30e31f98772a1dd316a6071d1" }, { "type": "ADVISORY", "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90015.json" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90015" }, { "type": "PACKAGE", "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git" } ], "schema_version": "1.9.0", "summary": "xhci: fix lost bounce buffers on TDs spanning several ring segments" }