CVE-2026-90303: ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults
Noroxi assessment
Priority: Monitor (action score 0/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).
- Fixed version: Linux Linux 07e4d5380f2a844ab7a1b440dde350caf561cbb0, 1039bffd6ae9c75b42b7d148d6c1106134107b66, 2a14d7797a49a47bccd1a9327fd69da838dcb0dd.
Low priority for now. Upgrade to Linux Linux 07e4d5380f2a844ab7a1b440dde350caf561cbb0, 1039bffd6ae9c75b42b7d148d6c1106134107b66, 2a14d7797a49a47bccd1a9327fd69da838dcb0dd 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: ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults When CONFIG_DEBUG_USER=y, and cmdline "user_debug=31" is set, a user fault may trigger show_pte() without any lock. If another thread in the same process concurrently calls munmap(), the page table pages may be freed while show_pte() is still traversing them, causing a use-after-free in show_pte(). If CONFIG_ARM_LPAE=y, this may cause a kernel panic if the pages table of PMD are freed when show_pte() is running. Acquire mmap_write_lock() around show_pte() for user faults to fix the contention. For user faults, additionally restrict that show_pte() is called only when the addr is a user-space address (addr < TASK_SIZE). This is because the lock of tsk->mm only protects the virtual memory of user address space, furthermore, dumping the page tables of a kernel-space address for user faults is unnecessary and may have security implications. Keep everything unchanged for kernel faults, because the kernel is already in the "oops" state, acquiring a lock may risk a deadlock.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- 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.
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
- 4.0affected
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before ab14f07952adfe735d86a53518f8cd576dfd5892affected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 07e4d5380f2a844ab7a1b440dde350caf561cbb0affected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 2a14d7797a49a47bccd1a9327fd69da838dcb0ddaffected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 63e3c958a602d0896a101a897c2361878c266ca7affected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 59bbf86d0ff9373bfa033ca123c1e924f09f1ebaaffected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before c71f9a56520b419e55d173052629f2324deb5549affected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 720408d98d9fb3c91a12090436734c8c61f04545affected · git
- 6d021b724481fbb908eb29384898deb9f00dfe70 and later · before 1039bffd6ae9c75b42b7d148d6c1106134107b66affected · git
- before 4.0not 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:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.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-2026-90301Sep 17, 2026 · ocfs2: o2hb: quiesce negotiate handlers and timeout work32Monitor
- ← EarlierCVE-2026-90302Sep 17, 2026 · ocfs2: synchronize heartbeat callbacks with o2net teardown0Monitor
- Later →CVE-2026-90304Sep 17, 2026 · ARM: 9484/1: enable interrupts when unhandled user faults are triggered0Monitor
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 | 07e4d5380f2a844ab7a1b440dde350caf561cbb0 | Vendor (CNA) |
| Linux Linux | 1039bffd6ae9c75b42b7d148d6c1106134107b66 | Vendor (CNA) |
| Linux Linux | 2a14d7797a49a47bccd1a9327fd69da838dcb0dd | Vendor (CNA) |
| Linux Linux | 59bbf86d0ff9373bfa033ca123c1e924f09f1eba | Vendor (CNA) |
| Linux Linux | 63e3c958a602d0896a101a897c2361878c266ca7 | Vendor (CNA) |
| Linux Linux | 720408d98d9fb3c91a12090436734c8c61f04545 | Vendor (CNA) |
| Linux Linux | ab14f07952adfe735d86a53518f8cd576dfd5892 | Vendor (CNA) |
| Linux Linux | c71f9a56520b419e55d173052629f2324deb5549 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (7 more)Show less
- git.kernel.org/stable/c/1039bffd6ae9c75b42b7d148d6c1106134107b66
- git.kernel.org/stable/c/2a14d7797a49a47bccd1a9327fd69da838dcb0dd
- git.kernel.org/stable/c/59bbf86d0ff9373bfa033ca123c1e924f09f1eba
- git.kernel.org/stable/c/63e3c958a602d0896a101a897c2361878c266ca7
- git.kernel.org/stable/c/720408d98d9fb3c91a12090436734c8c61f04545
- git.kernel.org/stable/c/ab14f07952adfe735d86a53518f8cd576dfd5892
- git.kernel.org/stable/c/c71f9a56520b419e55d173052629f2324deb5549
Vendor advisories and official records. Exploit/PoC links are deliberately left out.