CVE-2025-38326: aoe: clean device rq_list in aoedev_downdev()
Noroxi assessment
Priority: Monitor (action score 22/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.22% (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 00be74e1470af292c37a438b8e69dee47dcbf481, 531aef4a1accb13b21a3b82ec29955f4733367d5, 64fc0bad62ed38874131dd0337d844a43bd1017e; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
Low priority for now. Upgrade to Linux Linux 00be74e1470af292c37a438b8e69dee47dcbf481, 531aef4a1accb13b21a3b82ec29955f4733367d5, 64fc0bad62ed38874131dd0337d844a43bd1017e; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 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: aoe: clean device rq_list in aoedev_downdev() An aoe device's rq_list contains accepted block requests that are waiting to be transmitted to the aoe target. This queue was added as part of the conversion to blk_mq. However, the queue was not cleaned out when an aoe device is downed which caused blk_mq_freeze_queue() to sleep indefinitely waiting for those requests to complete, causing a hang. This fix cleans out the queue before calling blk_mq_freeze_queue().
- Published
- Jul 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
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
- 4.20affected
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before ed52e9652ba41d362e9ec923077f6da23336f269affected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before 64fc0bad62ed38874131dd0337d844a43bd1017eaffected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before ef0b5bbbed7f220db2e9c73428f9a36e8dfc69caaffected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before 531aef4a1accb13b21a3b82ec29955f4733367d5affected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before 8662ac79a63488e279b91c12a72b02bc0dc49f7baffected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before fa2a79f0da92614c5dc45c8b3d2638681c7734eeaffected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before 00be74e1470af292c37a438b8e69dee47dcbf481affected · git
- 3582dd291788e9441c3ba9047e55089edb98da5c and later · before 7f90d45e57cb2ef1f0adcaf925ddffdfc5e680caaffected · git
- before 4.20not affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.5 and later · before 5.10.239
- linux linux kernel5.11 and later · before 5.15.186
- linux linux kernel5.16 and later · before 6.1.142
- linux linux kernel4.20 and later · before 5.4.295
- linux linux kernel6.7 and later · before 6.12.35
- linux linux kernel6.13 and later · before 6.15.4
- linux linux kernel6.2 and later · before 6.6.95
- linux linux kernel6.16
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.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.35-1 | 6.12.35-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-2025-38319Jul 10, 2025 · drm/amd/pp: Fix potential NULL pointer dereference in atomctrl_initialize_mc_reg_table22Monitor
- ← EarlierCVE-2025-38325Jul 10, 2025 · ksmbd: add free_transport ops in ksmbd connection22Monitor
- Later →CVE-2025-38327Jul 10, 2025 · fgraph: Do not enable function_graph tracer when setting funcgraph-args22Monitor
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 | 00be74e1470af292c37a438b8e69dee47dcbf481 | Vendor (CNA) |
| Linux Linux | 531aef4a1accb13b21a3b82ec29955f4733367d5 | Vendor (CNA) |
| Linux Linux | 64fc0bad62ed38874131dd0337d844a43bd1017e | Vendor (CNA) |
| Linux Linux | 7f90d45e57cb2ef1f0adcaf925ddffdfc5e680ca | Vendor (CNA) |
| Linux Linux | 8662ac79a63488e279b91c12a72b02bc0dc49f7b | Vendor (CNA) |
| Linux Linux | ed52e9652ba41d362e9ec923077f6da23336f269 | Vendor (CNA) |
| Linux Linux | ef0b5bbbed7f220db2e9c73428f9a36e8dfc69ca | Vendor (CNA) |
| Linux Linux | fa2a79f0da92614c5dc45c8b3d2638681c7734ee | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.147-1 · Debian:12 | 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.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 (9 more)Show less
- git.kernel.org/stable/c/531aef4a1accb13b21a3b82ec29955f4733367d5
- git.kernel.org/stable/c/64fc0bad62ed38874131dd0337d844a43bd1017e
- git.kernel.org/stable/c/7f90d45e57cb2ef1f0adcaf925ddffdfc5e680ca
- git.kernel.org/stable/c/8662ac79a63488e279b91c12a72b02bc0dc49f7b
- git.kernel.org/stable/c/ed52e9652ba41d362e9ec923077f6da23336f269
- git.kernel.org/stable/c/ef0b5bbbed7f220db2e9c73428f9a36e8dfc69ca
- git.kernel.org/stable/c/fa2a79f0da92614c5dc45c8b3d2638681c7734ee
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.