{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90015 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90015 is a vulnerability in Linux, published on 16 Sep 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-90015 and fix it if it is affected.\n\nWhat it is: CVE-2026-90015 is a vulnerability in Linux, published on 16 Sep 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-90015 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-90015/ (Markdown: https://insights.sbomify.com/CVE-2026-90015/index.md)","id":"CVE-2026-90015","markdown":"https://insights.sbomify.com/CVE-2026-90015/index.md","name":"CVE-2026-90015","record":{"aliases":["AZL-101210","BELL-CVE-2026-90015","DEBIAN-CVE-2026-90015","GHSA-vp4r-2v9h-p25v","UBUNTU-CVE-2026-90015"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"none","summary":"A flaw in the Linux kernel xHCI driver allows attackers with physical USB access to leak memory contents or cause data corruption via large fragmented transfers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\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.]","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":"xhci: fix lost bounce buffers on TDs spanning several ring segments","id":"CVE-2026-90015","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()","id":"CVE-2026-90016"},"packages":[],"prev":{"headline":"tracing: Have show_event_filters/triggers files take trace array ref","id":"CVE-2026-90014"},"products":["Linux"],"published":"2026-09-16","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 flaw in the Linux kernel xHCI driver allows attackers with physical USB access to leak memory contents or cause data corruption via large fragmented transfers.","url":"https://insights.sbomify.com/CVE-2026-90015/"}