CVE-2026-98722: mtd: block2mtd: Fix divide error when erase_size is zero
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 21d0f05989bf0d5cef57b467a7fa4feefbd7236a, 7ad5287e58d7aa1a848105f119e6c5b00446882f, 826170a49ca1315af6b293a02200585b1e2186d9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 21d0f05989bf0d5cef57b467a7fa4feefbd7236a, 7ad5287e58d7aa1a848105f119e6c5b00446882f, 826170a49ca1315af6b293a02200585b1e2186d9; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes 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: block2mtd: Fix divide error when erase_size is zero The erase size is parsed from the "block2mtd" module parameter and can be set to zero. add_device() then evaluates if (size % erase_size) with a zero divisor, which triggers a divide error: divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ... Reject a zero erase size before performing the modulo operation so the existing "erasesize must be a divisor of device size" error path reports the invalid argument and frees the device.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th 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.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.
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
- 3.15affected
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before c8004de07739fa9a39e310e859384f1458d7d076affected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before 7ad5287e58d7aa1a848105f119e6c5b00446882faffected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before fd73c079abc58e10183a4db4dc9dc5012db17476affected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before bff83b723e93acc788bd690dc4bc1f6f4356c35baffected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before 826170a49ca1315af6b293a02200585b1e2186d9affected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before a991c28066e7ba4da7450bb04478849f7ac6a14aaffected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before 21d0f05989bf0d5cef57b467a7fa4feefbd7236aaffected · git
- ea6d833a3fddcd1d60414d48f34c7f4fbe88608f and later · before b5965c4221165045e19736794ca5f48ae3d67142affected · git
- before 3.15not 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 | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-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-98720Oct 18, 2026 · KVM: nVMX: Force MSR bitmap refresh if runtime eVMCS controls are modified0Monitor
- ← EarlierCVE-2026-98721Oct 18, 2026 · mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ0Monitor
- Later →CVE-2026-98723Oct 18, 2026 · nvmet: copy the hostid into the ctrl before creating PR pc_refs0Monitor
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 | 21d0f05989bf0d5cef57b467a7fa4feefbd7236a | Vendor (CNA) |
| Linux Linux | 7ad5287e58d7aa1a848105f119e6c5b00446882f | Vendor (CNA) |
| Linux Linux | 826170a49ca1315af6b293a02200585b1e2186d9 | Vendor (CNA) |
| Linux Linux | a991c28066e7ba4da7450bb04478849f7ac6a14a | Vendor (CNA) |
| Linux Linux | b5965c4221165045e19736794ca5f48ae3d67142 | Vendor (CNA) |
| Linux Linux | bff83b723e93acc788bd690dc4bc1f6f4356c35b | Vendor (CNA) |
| Linux Linux | c8004de07739fa9a39e310e859384f1458d7d076 | Vendor (CNA) |
| Linux Linux | fd73c079abc58e10183a4db4dc9dc5012db17476 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayNov 6, 2026+19 d
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/7ad5287e58d7aa1a848105f119e6c5b00446882f
- git.kernel.org/stable/c/826170a49ca1315af6b293a02200585b1e2186d9
- git.kernel.org/stable/c/a991c28066e7ba4da7450bb04478849f7ac6a14a
- git.kernel.org/stable/c/b5965c4221165045e19736794ca5f48ae3d67142
- git.kernel.org/stable/c/bff83b723e93acc788bd690dc4bc1f6f4356c35b
- git.kernel.org/stable/c/c8004de07739fa9a39e310e859384f1458d7d076
- git.kernel.org/stable/c/fd73c079abc58e10183a4db4dc9dc5012db17476
Vendor advisories and official records. Exploit/PoC links are deliberately left out.