CVE-2026-43250: usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1497998749600411d75e60a44f7e572b2348bd9a, 1b72b834511d17f4d069d512f78671f3f210a2f1, aad97c92119cb85db105ddda4a44c86cc0748e8c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1497998749600411d75e60a44f7e572b2348bd9a, 1b72b834511d17f4d069d512f78671f3f210a2f1, aad97c92119cb85db105ddda4a44c86cc0748e8c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() The ChipIdea UDC driver can encounter "not page aligned sg buffer" errors when a USB device is reconnected after being disconnected during an active transfer. This occurs because _ep_nuke() returns requests to the gadget layer without properly unmapping DMA buffers or cleaning up scatter-gather bounce buffers. Root cause: When a disconnect happens during a multi-segment DMA transfer, the request's num_mapped_sgs field and sgt.sgl pointer remain set with stale values. The request is returned to the gadget driver with status -ESHUTDOWN but still has active DMA state. If the gadget driver reuses this request on reconnect without reinitializing it, the stale DMA state causes _hardware_enqueue() to skip DMA mapping (seeing non-zero num_mapped_sgs) and attempt to use freed/invalid DMA addresses, leading to alignment errors and potential memory corruption. The normal completion path via _hardware_dequeue() properly calls usb_gadget_unmap_request_by_dev() and sglist_do_debounce() before returning the request. The _ep_nuke() path must do the same cleanup to ensure requests are returned in a clean, reusable state. Fix: Add DMA unmapping and bounce buffer cleanup to _ep_nuke() to mirror the cleanup sequence in _hardware_dequeue(): - Call usb_gadget_unmap_request_by_dev() if num_mapped_sgs is set - Call sglist_do_debounce() with copy=false if bounce buffer exists This ensures that when requests are returned due to endpoint shutdown, they don't retain stale DMA mappings. The 'false' parameter to sglist_do_debounce() prevents copying data back (appropriate for shutdown path where transfer was aborted).
- Published
- May 6, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-787
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.29affected
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before 1497998749600411d75e60a44f7e572b2348bd9aaffected · git
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before aad97c92119cb85db105ddda4a44c86cc0748e8caffected · git
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before 1b72b834511d17f4d069d512f78671f3f210a2f1affected · git
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before f4fbf2d4750d12ac8525d2efac1016fa0d84d4ecaffected · git
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before e74c436f8568af1c60942469d0a2300b3ada3857affected · git
- aa69a8093ff985873cb44fe1157bd6db29a20fe4 and later · before cea2a1257a3b5ea3e769a445b34af13e6aa5a123affected · git
- before 2.6.29not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.29 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43248May 6, 2026 · vhost: move vdpa group bound check to vhost_vdpa31Monitor
- ← EarlierCVE-2026-43249May 6, 2026 · 9p/xen: protect xen_9pfs_front_free against concurrent calls35Monitor
- Later →CVE-2026-43251May 6, 2026 · HID: prodikeys: Check presence of pm->input_ep8222Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1497998749600411d75e60a44f7e572b2348bd9a | Vendor (CNA) |
| Linux Linux | 1b72b834511d17f4d069d512f78671f3f210a2f1 | Vendor (CNA) |
| Linux Linux | aad97c92119cb85db105ddda4a44c86cc0748e8c | Vendor (CNA) |
| Linux Linux | cea2a1257a3b5ea3e769a445b34af13e6aa5a123 | Vendor (CNA) |
| Linux Linux | e74c436f8568af1c60942469d0a2300b3ada3857 | Vendor (CNA) |
| Linux Linux | f4fbf2d4750d12ac8525d2efac1016fa0d84d4ec | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0196 · May 8, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1b72b834511d17f4d069d512f78671f3f210a2f1
- git.kernel.org/stable/c/aad97c92119cb85db105ddda4a44c86cc0748e8c
- git.kernel.org/stable/c/cea2a1257a3b5ea3e769a445b34af13e6aa5a123
- git.kernel.org/stable/c/e74c436f8568af1c60942469d0a2300b3ada3857
- git.kernel.org/stable/c/f4fbf2d4750d12ac8525d2efac1016fa0d84d4ec
Vendor advisories and official records. Exploit/PoC links are deliberately left out.