CVE-2026-63800

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-45466 (ENISA EUVD) · GHSA-fjxq-h4gg-vf5r (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

pNFS: Fix use-after-free in pnfs_update_layout()

When hitting the NFS_LAYOUT_RETURN branch in pnfs_update_layout(), the code calls pnfs_prepare_to_retry_layoutget(lo). If it succeeds, pnfs_put_layout_hdr(lo) is called before trace_pnfs_update_layout(), which still references 'lo'. This results in a use-after-free when the tracepoint accesses lo's fields.

Fix this by moving the tracepoint call before pnfs_put_layout_hdr(lo).

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
50th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 19, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Oct 27, 2026
Patch available.
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c0fb5c09ae5bd68dc0038692af8127029cb0385
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9645aaf689aff57427ece3b9fa47d5b5399417f4
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e37e9b3e82ade881e1798e2f4fcc54aff7793c1
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ad8b9a85dbf57ca532ee9e65ad7e6498bfbbf98
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2883ddd7542b4437a2ab4908fe2773f690e20889
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/200e7637f4d6a1342987045eea72641524f909dc
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f24b8302c77dcaf79c64c073877a3b9f4dd25d2
Web page

pNFS: Fix use-after-free in pnfs_update_layout() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13e198a90ca4050f4bee8a3f23680389a6563ccc

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1111.117~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-27ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.194.171) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1068.68) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1110.108) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1110.114~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-fips-5.15 (5.15.0.194.113) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1079 (5.15.0-1079.83) @ jammy2026-10-27ubuntu
redhatkernel-0:5.14.0-687.44.1.el9_82026-09-04redhat
redhatkernel-rt-0:4.18.0-553.159.1.rt7.500.el8_102026-09-03redhat
redhatkernel-0:4.18.0-553.159.1.el8_102026-09-03redhat
redhatkernel-0:6.12.0-211.50.1.el10_22026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)
  • every version up to 5.10.262-1: fixed in 5.10.262-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)
  • every version up to 6.1.177-1~deb11u1: fixed in 6.1.177-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)
  • every version up to 6.1.177-1: fixed in 6.1.177-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)
  • every version up to 6.12.95-1: fixed in 6.12.95-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)
  • every version up to 7.1.3-1: fixed in 7.1.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 31× in last 7d / 99× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 543 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 443 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-10-27 09:19 UTCEG score recompute
  3. 2026-10-27 09:19 UTCVendor advisory
  4. 2026-10-27 09:18 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  6. 2026-10-26 10:29 UTCEG score recompute
  7. 2026-10-26 10:29 UTCVendor advisory
  8. 2026-10-26 10:28 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-10-25 14:13 UTCEG score recompute
  11. 2026-10-25 12:06 UTCEG score recompute
  12. 2026-10-25 12:06 UTCVendor advisory
  13. 2026-10-25 12:05 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-24 13:39 UTCEG score recompute
  16. 2026-10-24 13:39 UTCVendor advisory
  17. 2026-10-24 13:38 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-23 15:11 UTCVendor advisory
  20. 2026-10-23 15:11 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-22 16:47 UTCEG score recompute
  22. 2026-10-22 16:47 UTCVendor advisory
  23. 2026-10-22 16:47 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-21 17:29 UTCEG score recompute
Show 75 more
  1. 2026-10-21 17:29 UTCVendor advisory
  2. 2026-10-21 17:29 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-20 18:43 UTCEG score recompute
  5. 2026-10-20 18:43 UTCVendor advisory
  6. 2026-10-20 18:43 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-19 20:19 UTCEG score recompute
  9. 2026-10-19 20:19 UTCVendor advisory
  10. 2026-10-19 20:19 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-19 13:38 UTCEG score recompute
  13. 2026-10-19 13:38 UTCVendor advisory
  14. 2026-10-19 13:37 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-18 13:28 UTCVendor advisory
  17. 2026-10-18 13:27 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-18 03:23 UTCEG score recompute
  19. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-17 15:03 UTCEG score recompute
  21. 2026-10-17 15:03 UTCVendor advisory
  22. 2026-10-17 15:03 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-16 16:38 UTCEG score recompute
  25. 2026-10-16 16:38 UTCVendor advisory
  26. 2026-10-16 16:36 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-16 15:41 UTCEG score recompute
  28. 2026-10-16 15:40 UTCVendor advisory
  29. 2026-10-16 15:40 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-16 12:23 UTCEG score recompute
  31. 2026-10-16 12:23 UTCVendor advisory
  32. 2026-10-16 12:22 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-10-15 13:58 UTCEG score recompute
  35. 2026-10-15 13:58 UTCVendor advisory
  36. 2026-10-15 13:57 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-10-14 08:49 UTCEG score recompute
  39. 2026-10-14 08:49 UTCVendor advisory
  40. 2026-10-14 08:49 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-10-13 04:36 UTCEG score recompute
  43. 2026-10-13 04:36 UTCVendor advisory
  44. 2026-10-13 04:36 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-10-12 15:48 UTCEG score recompute
  47. 2026-10-12 06:13 UTCVendor advisory
  48. 2026-10-12 06:12 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-11 19:33 UTCEG score recompute
  50. 2026-10-11 16:48 UTCEG score recompute
  51. 2026-10-11 14:09 UTCEG score recompute
  52. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  53. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  54. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  55. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  56. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  57. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  58. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  59. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  60. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  61. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  62. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  63. 2026-10-01 13:14 UTCVendor advisory
  64. 2026-10-01 13:13 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-01 09:11 UTCEG score recompute
  66. 2026-10-01 09:11 UTCVendor advisory
  67. 2026-10-01 09:11 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  69. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  70. 2026-09-28 13:13 UTCVendor advisory
  71. 2026-09-28 13:12 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-28 07:42 UTCEG score recompute
  73. 2026-09-28 07:42 UTCVendor advisory
  74. 2026-09-28 07:42 UTCGHSA enrichmentGHSA-fjxq-h4gg-vf5r · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile

Frequently asked(5)

What is CVE-2026-63800?
CVE-2026-63800 is a critical-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: pNFS: Fix use-after-free in pnfsupdatelayout() When hitting the NFSLAYOUTRETURN branch in pnfsupdatelayout(), the code calls pnfspreparetoretrylayoutget(lo). If it succeeds, pnfsputlayouthdr(lo) is called before…
When was the CVE record for CVE-2026-63800 published?
The CVE record for CVE-2026-63800 was published on July 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-63800 actively exploited?
CVE-2026-63800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63800?
CVE-2026-63800 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63800?
A fix for CVE-2026-63800 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63800 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63800

Explore →

Is Your Infrastructure Affected by CVE-2026-63800?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.