CVE-2026-89525: udf: reject VAT indexes equal to the entry count
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 19f36c6453cd88fe6d60ef36ab1f1cad8ddf4ce4, 1bd7947f1463c21edafa256d0fbec5b99215e2b6, 8a8c1c42a34349a0626d910abbad5a29136446b7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 19f36c6453cd88fe6d60ef36ab1f1cad8ddf4ce4, 1bd7947f1463c21edafa256d0fbec5b99215e2b6, 8a8c1c42a34349a0626d910abbad5a29136446b7 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: udf: reject VAT indexes equal to the entry count UDF 1.50 virtual partition mapping uses the VAT as an array of physical block mappings. s_num_entries stores the number of entries in that array, not the highest valid index. The valid VAT indexes are therefore below s_num_entries. udf_get_pblock_virt15() currently rejects only indexes greater than s_num_entries. A crafted image can request index s_num_entries, pass the bounds check, and make the kernel read one entry past the allocated VAT table. Change the check to reject block >= s_num_entries, so the count is handled as an exclusive upper bound. A crafted UDF image reproduced this on origin/master commit 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53 with a KASAN slab-out-of-bounds report in udf_get_pblock_virt15(). Trail of Bits has a reproducer that triggers kernel panic demonstrating the bug, and can share it if needed.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th 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.
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.
—
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.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f64e01a90326bb85a3cc8aa0199931dc2f15b589affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8a8c1c42a34349a0626d910abbad5a29136446b7affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 19f36c6453cd88fe6d60ef36ab1f1cad8ddf4ce4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b77b83f5529a26d084d64ece98abd6f0cc86e053affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9193368408d792cec2057628d87862140fb1ce1caffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b95c33a4e743874f1b0a45bf2aaa4da553552bd1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1bd7947f1463c21edafa256d0fbec5b99215e2b6affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before cac0cb07f29ccfb373fd4a36c81e908ef3ce608caffected · git
- before 2.6.12not 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 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.8-1.1 | 7.2.8-1.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-89523Sep 11, 2026 · wifi: mt76: mt7925: cancel pending mlo_pm_work31Monitor
- ← EarlierCVE-2026-89524Sep 11, 2026 · wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets32Monitor
- Later →CVE-2026-89526Sep 11, 2026 · svcrdma: Validate Read chunk positions before reconstruction39Monitor
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 | 19f36c6453cd88fe6d60ef36ab1f1cad8ddf4ce4 | Vendor (CNA) |
| Linux Linux | 1bd7947f1463c21edafa256d0fbec5b99215e2b6 | Vendor (CNA) |
| Linux Linux | 8a8c1c42a34349a0626d910abbad5a29136446b7 | Vendor (CNA) |
| Linux Linux | 9193368408d792cec2057628d87862140fb1ce1c | Vendor (CNA) |
| Linux Linux | b77b83f5529a26d084d64ece98abd6f0cc86e053 | Vendor (CNA) |
| Linux Linux | b95c33a4e743874f1b0a45bf2aaa4da553552bd1 | Vendor (CNA) |
| Linux Linux | cac0cb07f29ccfb373fd4a36c81e908ef3ce608c | Vendor (CNA) |
| Linux Linux | f64e01a90326bb85a3cc8aa0199931dc2f15b589 | 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) |
| opensuse:kernel-source | 7.2.8-1.1 · openSUSE:Tumbleweed | 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
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/1bd7947f1463c21edafa256d0fbec5b99215e2b6
- git.kernel.org/stable/c/8a8c1c42a34349a0626d910abbad5a29136446b7
- git.kernel.org/stable/c/9193368408d792cec2057628d87862140fb1ce1c
- git.kernel.org/stable/c/b77b83f5529a26d084d64ece98abd6f0cc86e053
- git.kernel.org/stable/c/b95c33a4e743874f1b0a45bf2aaa4da553552bd1
- git.kernel.org/stable/c/cac0cb07f29ccfb373fd4a36c81e908ef3ce608c
- git.kernel.org/stable/c/f64e01a90326bb85a3cc8aa0199931dc2f15b589
Vendor advisories and official records. Exploit/PoC links are deliberately left out.