CVE-2026-89557: md: do overflow check for sb->bblog_shift in super_1_load()
Noroxi assessment
Priority: Monitor (action score 31/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 0a03f9541c06fda64301dcf94f376f07ce2cc396, 323f3a056dbccb39a642ebde642044a680f3a6d6, 35d522bd32462afcf1981dab6da8a9256c26c1e0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0a03f9541c06fda64301dcf94f376f07ce2cc396, 323f3a056dbccb39a642ebde642044a680f3a6d6, 35d522bd32462afcf1981dab6da8a9256c26c1e0 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: md: do overflow check for sb->bblog_shift in super_1_load() In super_1_load(), sb->bblog_shift is an __u8 type value loaded from on- disk superblock. It is used for badblocks API badblocks_set() by the following sequence, 1930 rdev->badblocks.shift = sb->bblog_shift; 1931 for (i = 0 ; i < (sectors << (9-3)) ; i++, bbp++) { 1932 u64 bb = le64_to_cpu(*bbp); 1933 int count = bb & (0x3ff); 1934 u64 sector = bb >> 10; 1935 sector <<= sb->bblog_shift; 1936 count <<= sb->bblog_shift; 1937 if (bb + 1 == 0) 1938 break; 1939 if (!badblocks_set(&rdev->badblocks, sector, count, 1)) 1940 return -EINVAL; 1941 } bb->bblog_shit is in range of 0-255, variable sector is 64bit width, for an invalid bb->bblog_shit, it is possible to make sector be overflowed by the following calculation, 1935 sector <<= sb->bblog_shift; Then in turn when call badblocks_set() at line 1939 with the invalid rdev->badblocks.shift set at line 1930, may result an overflow inside _badblocks_clear() in block/badblocks.c. Although there are many places to call badblocks APIs, the non-zero shift value is only used in super_1_load(), other places always use 0 as the shift value. Therefore it is unnecessary to do a general shift value overflow check inside badblock API, and just check here as the caller. This may avoid unnecessary check, make the badblocks API code more simple and elegant.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.1affected
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 94c820d99a4305d4ded41a97ed37ec7d26c56e7faffected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 573fb68105fdc6a127ba6069e58a0d2aff3c9f93affected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 323f3a056dbccb39a642ebde642044a680f3a6d6affected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 0a03f9541c06fda64301dcf94f376f07ce2cc396affected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 75d15738fd33a782606d0dc80cfeff47edf2ddd8affected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 3b097416b4cff77285c1f472fc2c4058d8a7554faffected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before df7d4d011d5ace20699ea948712f09f9ac08924faffected · git
- 2699b67223aca6b1450fc2f72e40fada952afc85 and later · before 35d522bd32462afcf1981dab6da8a9256c26c1e0affected · git
- before 3.1not 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-89555Sep 11, 2026 · mpls: reload header after pskb_may_pull()39Monitor
- ← EarlierCVE-2026-89556Sep 11, 2026 · module: validate string table section types0Monitor
- Later →CVE-2026-89558Sep 11, 2026 · md/raid10: fix still_degraded being inverted in raid10_sync_request()39Monitor
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 | 0a03f9541c06fda64301dcf94f376f07ce2cc396 | Vendor (CNA) |
| Linux Linux | 323f3a056dbccb39a642ebde642044a680f3a6d6 | Vendor (CNA) |
| Linux Linux | 35d522bd32462afcf1981dab6da8a9256c26c1e0 | Vendor (CNA) |
| Linux Linux | 3b097416b4cff77285c1f472fc2c4058d8a7554f | Vendor (CNA) |
| Linux Linux | 573fb68105fdc6a127ba6069e58a0d2aff3c9f93 | Vendor (CNA) |
| Linux Linux | 75d15738fd33a782606d0dc80cfeff47edf2ddd8 | Vendor (CNA) |
| Linux Linux | 94c820d99a4305d4ded41a97ed37ec7d26c56e7f | Vendor (CNA) |
| Linux Linux | df7d4d011d5ace20699ea948712f09f9ac08924f | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → 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/323f3a056dbccb39a642ebde642044a680f3a6d6
- git.kernel.org/stable/c/35d522bd32462afcf1981dab6da8a9256c26c1e0
- git.kernel.org/stable/c/3b097416b4cff77285c1f472fc2c4058d8a7554f
- git.kernel.org/stable/c/573fb68105fdc6a127ba6069e58a0d2aff3c9f93
- git.kernel.org/stable/c/75d15738fd33a782606d0dc80cfeff47edf2ddd8
- git.kernel.org/stable/c/94c820d99a4305d4ded41a97ed37ec7d26c56e7f
- git.kernel.org/stable/c/df7d4d011d5ace20699ea948712f09f9ac08924f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.