mtd: mtdoops: free page bitmap when the backing MTD is removed
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 1e5cd8bc902331ff801df88cbb299029ae062753, 477d61d54e097e90f748aa18d013805abd56bcbd, 698944132083d143ef965c0090ee14ba1d9e1a5f; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1e5cd8bc902331ff801df88cbb299029ae062753, 477d61d54e097e90f748aa18d013805abd56bcbd, 698944132083d143ef965c0090ee14ba1d9e1a5f; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.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: mtd: mtdoops: free page bitmap when the backing MTD is removed mtdoops_notify_add() allocates oops_page_used when the configured MTD device is registered. mtdoops_notify_remove() detaches from that device but leaves the bitmap allocated. If the same MTD device is later registered again, the add path allocates a new bitmap and overwrites the old pointer, leaking one vmalloc allocation per remove/add cycle. This is only visible when the backing MTD device can disappear and be registered again while mtdoops remains loaded, so the usual static MTD case does not expose it. Free the bitmap after unregistering the dumper and flushing the pending workers, then clear the pointer and page count before a later attach can allocate fresh state. Clearing the pointer also keeps the module exit path from freeing the same bitmap a second time after a remove event.
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.2% · 10th 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
- 2.6.33affected
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before 477d61d54e097e90f748aa18d013805abd56bcbdaffected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before a91ac71e67c3e01ed9afd9841435bebb930293f8affected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before 698944132083d143ef965c0090ee14ba1d9e1a5faffected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before f25c804947e0a28c15e73da8e2e0db959cbed716affected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before 8414f0e9f707226de20b48c7048179fd86d352fcaffected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before d06f91a52af11630c9f7e487f6daf242ac310cb8affected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before 1e5cd8bc902331ff801df88cbb299029ae062753affected · git
- be95745f01677245a061a8f51473ef5ec8ad008e and later · before 956e7da12c114f13c63d126ab1d79c3b6a819060affected · git
- before 2.6.33not 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
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
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 | 1e5cd8bc902331ff801df88cbb299029ae062753 | Vendor (CNA) |
| Linux Linux | 477d61d54e097e90f748aa18d013805abd56bcbd | Vendor (CNA) |
| Linux Linux | 698944132083d143ef965c0090ee14ba1d9e1a5f | Vendor (CNA) |
| Linux Linux | 8414f0e9f707226de20b48c7048179fd86d352fc | Vendor (CNA) |
| Linux Linux | 956e7da12c114f13c63d126ab1d79c3b6a819060 | Vendor (CNA) |
| Linux Linux | a91ac71e67c3e01ed9afd9841435bebb930293f8 | Vendor (CNA) |
| Linux Linux | d06f91a52af11630c9f7e487f6daf242ac310cb8 | Vendor (CNA) |
| Linux Linux | f25c804947e0a28c15e73da8e2e0db959cbed716 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
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/477d61d54e097e90f748aa18d013805abd56bcbd
- git.kernel.org/stable/c/698944132083d143ef965c0090ee14ba1d9e1a5f
- git.kernel.org/stable/c/8414f0e9f707226de20b48c7048179fd86d352fc
- git.kernel.org/stable/c/956e7da12c114f13c63d126ab1d79c3b6a819060
- git.kernel.org/stable/c/a91ac71e67c3e01ed9afd9841435bebb930293f8
- git.kernel.org/stable/c/d06f91a52af11630c9f7e487f6daf242ac310cb8
- git.kernel.org/stable/c/f25c804947e0a28c15e73da8e2e0db959cbed716
Vendor advisories and official records. Exploit/PoC links are deliberately left out.