CVE-2025-39920: pcmcia: Add error handling for add_interval() in do_validate_mem()
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.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 06b26e3099207c94b3d1be8565aedc6edc4f0a60, 289b58f8ff3198d091074a751d6b8f6827726f3e, 369bf6e241506583f4ee7593c53b92e5a9f271b4; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 06b26e3099207c94b3d1be8565aedc6edc4f0a60, 289b58f8ff3198d091074a751d6b8f6827726f3e, 369bf6e241506583f4ee7593c53b92e5a9f271b4; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.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: pcmcia: Add error handling for add_interval() in do_validate_mem() In the do_validate_mem(), the call to add_interval() does not handle errors. If kmalloc() fails in add_interval(), it could result in a null pointer being inserted into the linked list, leading to illegal memory access when sub_interval() is called next. This patch adds an error handling for the add_interval(). If add_interval() returns an error, the function will return early with the error code.
- Published
- Oct 1, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-476
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.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 |
| 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
- 2.6.34affected
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 5b60ed401b47897352c520bc724c85aa908dedccaffected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before ae184024ef31423e5beb44cf4f52999bbcf2fe5baffected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 85be7ef8c8e792a414940a38d94565dd48d2f236affected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 06b26e3099207c94b3d1be8565aedc6edc4f0a60affected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 8699358b6ac99b8ccc97ed9e6e3669ef8958ef7baffected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 289b58f8ff3198d091074a751d6b8f6827726f3eaffected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 369bf6e241506583f4ee7593c53b92e5a9f271b4affected · git
- 7b4884ca8853a638df0eb5d251d80d67777b8b1a and later · before 4a81f78caa53e0633cf311ca1526377d9bff7479affected · git
- before 2.6.34not 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.243
- linux linux kernel5.11 and later · before 5.15.192
- linux linux kernel5.16 and later · before 6.1.151
- linux linux kernel2.6.34 and later · before 5.4.299
- linux linux kernel6.7 and later · before 6.12.46
- linux linux kernel6.13 and later · before 6.16.6
- linux linux kernel6.2 and later · before 6.6.105
- linux linux kernel6.17
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.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.48-1 | 6.12.48-1 |
| Debian:14 | linux | before 6.16.6-1 | 6.16.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-2025-39918Oct 1, 2025 · wifi: mt76: fix linked list corruption22Monitor
- ← EarlierCVE-2025-39919Oct 1, 2025 · wifi: mt76: mt7996: add missing check for rx wcid entries22Monitor
- Later →CVE-2025-39921Oct 1, 2025 · spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback22Monitor
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 | 06b26e3099207c94b3d1be8565aedc6edc4f0a60 | Vendor (CNA) |
| Linux Linux | 289b58f8ff3198d091074a751d6b8f6827726f3e | Vendor (CNA) |
| Linux Linux | 369bf6e241506583f4ee7593c53b92e5a9f271b4 | Vendor (CNA) |
| Linux Linux | 4a81f78caa53e0633cf311ca1526377d9bff7479 | Vendor (CNA) |
| Linux Linux | 5b60ed401b47897352c520bc724c85aa908dedcc | Vendor (CNA) |
| Linux Linux | 85be7ef8c8e792a414940a38d94565dd48d2f236 | Vendor (CNA) |
| Linux Linux | 8699358b6ac99b8ccc97ed9e6e3669ef8958ef7b | Vendor (CNA) |
| Linux Linux | ae184024ef31423e5beb44cf4f52999bbcf2fe5b | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.153-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)
CWE-476 · NULL Pointer DereferenceCVSS 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/289b58f8ff3198d091074a751d6b8f6827726f3e
- git.kernel.org/stable/c/369bf6e241506583f4ee7593c53b92e5a9f271b4
- git.kernel.org/stable/c/4a81f78caa53e0633cf311ca1526377d9bff7479
- git.kernel.org/stable/c/5b60ed401b47897352c520bc724c85aa908dedcc
- git.kernel.org/stable/c/85be7ef8c8e792a414940a38d94565dd48d2f236
- git.kernel.org/stable/c/8699358b6ac99b8ccc97ed9e6e3669ef8958ef7b
- git.kernel.org/stable/c/ae184024ef31423e5beb44cf4f52999bbcf2fe5b
- 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.