Skip to content
Fencer Intel
high 7.5

CVE-2017-9763 json

The grub_ext2_read_block function in fs/ext2.c in GNU GRUB before 2013-11-12, as used in shlr/grub/fs/ext2.c in radare2 1.5.0, allows remot…

published 2017-06-19 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18693

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.1%
EPSS 4.1% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

The grub_ext2_read_block function in fs/ext2.c in GNU GRUB before 2013-11-12, as used in shlr/grub/fs/ext2.c in radare2 1.5.0, allows remote attackers to cause a denial of service (excessive stack use and application crash) via a crafted binary file, related to use of a variable-size stack array.

Patch / fix

  • grub2 Debian 14, Debian 13, Debian 12 2.02~beta2-8

debian advisories DEBIAN-CVE-2017-9763

  • grub2 SLES for SAP 11 SP4, SLES 11 SP4 2.00-0.66.8.1
  • grub2 SLES 11 SP4-LTSS 2.02-0.66.26.1

suse advisories SUSE-SU-2021:14659-1SUSE-SU-2019:13989-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-9763 updated cvss 3.3

grub2: Stack exhaustion in grub_ext2_read_block

  • Red Hat Enterprise Linux 5 grub Red Hat Enterprise Linux 6 grub Red Hat Enterprise Linux 7 grub2, grub2-pc, grub2-efi, grub2-ppc64, grub2-tools, grub2-common, +15 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.08% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.