CVE-2025-40172: accel/qaic: Treat remaining == 0 as error in find_and_map_user_pages()
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.15% (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 11f08c30a3e4157305ba692f1d44cca5fc9a8fca, 1ab9733d14cc9987cc5dcd1f0ad1f416e302e2e6, 48b1d42286bfef7628b1d6c8c28d4e456c90f725.
Low priority for now. Upgrade to Linux Linux 11f08c30a3e4157305ba692f1d44cca5fc9a8fca, 1ab9733d14cc9987cc5dcd1f0ad1f416e302e2e6, 48b1d42286bfef7628b1d6c8c28d4e456c90f725 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: accel/qaic: Treat remaining == 0 as error in find_and_map_user_pages() Currently, if find_and_map_user_pages() takes a DMA xfer request from the user with a length field set to 0, or in a rare case, the host receives QAIC_TRANS_DMA_XFER_CONT from the device where resources->xferred_dma_size is equal to the requested transaction size, the function will return 0 before allocating an sgt or setting the fields of the dma_xfer struct. In that case, encode_addr_size_pairs() will try to access the sgt which will lead to a general protection fault. Return an EINVAL in case the user provides a zero-sized ALP, or the device requests continuation after all of the bytes have been transferred.
- Published
- Nov 12, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- d410a96e5cb8c1ec7049c83f2edcd8bbfaf5d9b3, 6.5affected
- 96d3c1cadedb6ae2e8965e19cd12caa244afbd9c and later · before 48b1d42286bfef7628b1d6c8c28d4e456c90f725affected · git
- 96d3c1cadedb6ae2e8965e19cd12caa244afbd9c and later · before 551f1dfbcb7f3e6ed07f9d6c8c1c64337fcd0edeaffected · git
- 96d3c1cadedb6ae2e8965e19cd12caa244afbd9c and later · before 1ab9733d14cc9987cc5dcd1f0ad1f416e302e2e6affected · git
- 96d3c1cadedb6ae2e8965e19cd12caa244afbd9c and later · before 11f08c30a3e4157305ba692f1d44cca5fc9a8fcaaffected · git
- 6.4.12 and later · before 6.5affected · semver
- before 6.5not affected · semver
- 6.6.114 and later · up to and including 6.6.*not affected · semver
- 6.12.55 and later · up to and including 6.12.*not affected · semver
- 6.17.5 and later · up to and including 6.17.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.17.6-1 | 6.17.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40170Nov 12, 2025 · net: use dst_dev_rcu() in sk_setup_caps()31Monitor
- ← EarlierCVE-2025-40171Nov 12, 2025 · nvmet-fc: move lsop put work to nvmet_fc_ls_req_op30Monitor
- Later →CVE-2025-40173Nov 12, 2025 · net/ip6_tunnel: Prevent perpetual tunnel growth31Monitor
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 | 11f08c30a3e4157305ba692f1d44cca5fc9a8fca | Vendor (CNA) |
| Linux Linux | 1ab9733d14cc9987cc5dcd1f0ad1f416e302e2e6 | Vendor (CNA) |
| Linux Linux | 48b1d42286bfef7628b1d6c8c28d4e456c90f725 | Vendor (CNA) |
| Linux Linux | 551f1dfbcb7f3e6ed07f9d6c8c1c64337fcd0ede | Vendor (CNA) |
| Linux Linux | 6.5 | Vendor (CNA) |
| debian:linux | 6.12.57-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.